forked from clio/ten_years_rails
-
Notifications
You must be signed in to change notification settings - Fork 42
Add VALID_MODES constant and validate tracker mode at initialization #186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
JuanVqz
wants to merge
5
commits into
main
Choose a base branch
from
feature/valid-modes-constant
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
3ee8822
Add VALID_MODES constant and validate mode at initialization
JuanVqz 9e70ca4
Address code review feedback on valid modes refactor
JuanVqz 9c45948
Address review: fix mode validation gaps and centralize mode logic
JuanVqz 188fbfc
Add CHANGELOG entry for tracker mode validation
JuanVqz 121b69b
Refine mode error message and tidy mode specs
JuanVqz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| class DeprecationTracker | ||
| VALID_MODES = %i[save compare].freeze | ||
|
|
||
| # Human-readable list of valid modes for error messages and CLI help text. | ||
| def self.valid_modes_display | ||
| @valid_modes_display ||= VALID_MODES.map(&:to_s).join(", ") | ||
| end | ||
|
|
||
| def self.valid_mode?(mode) | ||
| mode && VALID_MODES.include?(mode.to_sym) | ||
| end | ||
| end |
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this guard skip the case where no
--tracker-modeis passed?--tracker-modeis optional, so on the documented defaultdeprecations run(README + the help examples)opts[:tracker_mode]isnil, andvalid_mode?(nil)is falsey, so this aborts withInvalid --tracker-mode nil.before reaching rspec.I cloned the branch and confirmed it:
deprecations run(no--tracker-mode) exits 1 on this branch, whereas onmainit falls through toDEPRECATION_TRACKER= bundle exec rspec ...and the library treats the blank value as the defaultsave. That blank-as-default path is exactly whatsanitize_modeadds for the library, but the CLI guard rejects nil/blank before that logic runs.What about only validating when a mode was actually supplied, so a genuine typo (
--tracker-mode bogus) still fails loudly but the default keeps working?