chore(lazygit): use git.pagers (array) instead of legacy git.paging#8
Open
ShortArrow wants to merge 1 commit into
Open
chore(lazygit): use git.pagers (array) instead of legacy git.paging#8ShortArrow wants to merge 1 commit into
ShortArrow wants to merge 1 commit into
Conversation
Lazygit replaced the singular `git.paging:` object with a plural `git.pagers:` array in v0.55.0 (the array form lets users cycle through multiple pager configs). The old key still works via a built-in migration handler (migratePagers in pkg/config/app_config.go), so this is a no-op for behavior — but rewriting the config in the modern shape avoids relying on the compatibility shim and keeps the file aligned with the current schema.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Rewrite
git.paging:(singular object) asgit.pagers:(one-element array) inlazygit/config.yml.Why
Lazygit replaced the singular
pagingobject with the pluralpagersarray in v0.55.0 — the array form lets users cycle through multiple pager configs. The old key still works becausemigratePagersinpkg/config/app_config.gosilently rewrites it at load time, but explicitly using the modern shape keeps the file aligned with the current schema and stops depending on the migration shim.Behavior is identical:
diff-so-fancycontinues to be used withcolorArg: always.Test plan
git.pagingis migrated togit.pagersautomatically since v0.55.0 — both forms produce the same runtime behavior.diff-so-fancyrendering remains intact on a commit diff view.