fix: correct pager default to false as intended by PR #1430#1642
fix: correct pager default to false as intended by PR #1430#1642
Conversation
📝 WalkthroughWalkthroughDefault CLI configuration changed: Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested labels
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Disabled knowledge base sources:
📒 Files selected for processing (1)
🧰 Additional context used📓 Path-based instructions (1)website/**📄 CodeRabbit inference engine (.cursor/rules/atmos-rules.mdc)
Files:
🪛 LanguageToolwebsite/blog/2025-10-15-pager-default-correction.md[style] ~16-~16: ‘with the intention of’ might be wordy. Consider a shorter alternative. (EN_WORDINESS_PREMIUM_WITH_THE_INTENTION_OF) [grammar] ~18-~18: There might be a mistake here. (QB_NEW_EN) [grammar] ~19-~19: There might be a mistake here. (QB_NEW_EN) [typographical] ~20-~20: Consider using a typographic opening quote here. (EN_QUOTES) [typographical] ~20-~20: Consider using a typographic close quote here. (EN_QUOTES) [grammar] ~82-~82: There might be a mistake here. (QB_NEW_EN) [grammar] ~83-~83: There might be a mistake here. (QB_NEW_EN) ⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Update test snapshots to reflect the corrected pager default value: - Change pager from "1" (true) to "0" (false) in describe configuration output - Remove "Failed to use pager" debug message from stderr (pager is now disabled by default) These changes align with the fix in the previous commit where the pager default was corrected to false as originally intended by PR #1430.
313ee61
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1642 +/- ##
==========================================
+ Coverage 64.97% 65.02% +0.04%
==========================================
Files 338 338
Lines 37535 37535
==========================================
+ Hits 24388 24406 +18
+ Misses 11201 11182 -19
- Partials 1946 1947 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
Add blog post explaining the regression and its fix: - Describes the history of the pager default issue - Explains impact on users - Provides migration guide for those who relied on pager being enabled - Links to relevant PRs and documentation This blog post helps users understand why the pager behavior may have changed and how to re-enable it if desired.
Change documentation link from /cli/configuration/settings#terminal-settings to /cli/configuration/terminal to fix broken link in blog post.
|
These changes were released in v1.195.0-test.0. |
what
v.SetDefault("settings.terminal.pager", true)tofalseinpkg/config/load.gowhy
setDefaultConfiguration()was never changed fromtruetofalsepager: falsein theiratmos.yamlatmos.yamlhaspager: falsewhich masked the issue locallyreferences
pkg/config/load.go:159Summary by CodeRabbit
Changes
Bug Fixes
Documentation