Do not warn on newlines in values #2397
Merged
Conversation
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
- Keep the warning on keys - Keep the warning for other "control" characters (like bell, backspace, ...) Also remove the newline from the example, and fix a few typos
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.
See #2302
So I think we should stop warning about it too.
This PR stops warning for newlines in values (replacing it by spaces, so "at position X" is not affected). It keeps warning for keys with newlines.
I didn't change the regex but opted for a
replacebecause:\p{Control}in regex that matches the same minus\n. I think[\u0000-\u0009\u000b\u001F\u007F-\u009F]is a lot less readable.Also remove the newline from the example, and fix a few typos