Move the annoying warning about the sloppy w/e/s/n one level up (GMT_MSG_INFORMATION) #8619
Conversation
This file contains 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
Esteban82
approved these changes
Nov 16, 2024
|
No need to test (I did it). |
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.
I propose to move the warning about the sloppy w/e/s/n one level up (require -Ii).
This warning shows up like
and I bet a large majority of users don't understand what we are talking about. On the other side, at least to me, that occurs with codes generated inside a wrapper where user has really no control on the exact w/e/s/n being asked, which will be modified anyway. So, for a bit sanity (perhaps mostly mine) let's move it up one level of verbosity.