-
-
Notifications
You must be signed in to change notification settings - Fork 15
feat: implement autofix for no-unnormalized-keys
#151
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
Draft
lumirlumir
wants to merge
9
commits into
main
Choose a base branch
from
feat-support-autofix-for-no-unnormalized-keys
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.
+165
−7
Draft
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
17318be
feat: implement autofix for `no-unnormalized-keys`
lumirlumir 4499d58
Merge branch 'main' into feat-support-autofix-for-no-unnormalized-keys
lumirlumir 42c637a
wip
lumirlumir 78c0ce5
wip: pin `rollup`
lumirlumir bd1dc6c
Merge branch 'main' into feat-support-autofix-for-no-unnormalized-keys
lumirlumir 58a24c7
wip: add more test cases
lumirlumir 1bfcd7d
wip
lumirlumir 16a61a1
wip
lumirlumir 5e5e7d8
wip: add more test
lumirlumir 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
Some comments aren't visible on the classic Files Changed page.
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
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.
This would produce incorrect fix if there are escape sequences, e.g.,
\n:Fixed to invalid JSON:
Also, I'm not sure if autofixing
\u1E9B\u0323toẛ̣instead of a sequence with\uXXXXwould be desirable.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.
Your suggestion also makes sense to me, but if that's the case, I have two questions:
Should
data.keybe updated accordingly?It seems

data.keyis displayed the same way:Is there a JavaScript (or other) rule I can refer to?
I don't have much experience with JSON (and JavaScript) rules, so I think I'm missing some edge cases while implementing the rule. Do you have any recommendations I could refer to when implementing the rule? If so, that would be very helpful.
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.
I think it would be better to show the raw key representation (i.e., as it appears in the linted source code) in the error message.
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.
I think the most similar thing we have in JS rules is a utility that parses string literals:
https://github.com/eslint/eslint/blob/main/lib/rules/utils/char-source.js
So we could try making something similar for JSON and use it to check how individual characters were represented in the original key and then try preserving the same form (a character directly inserted into the source code or an escape sequence) in the fixed key. A problem that might be difficult to solve in this particular rule is how to map characters from the fixed key to characters in the original key since the normalizations produce strings with different lengths.
Another option is to limit the autofix to keys that don't have escape sequences only.