We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have very large translation files that should be alphabetized according to the jsonc/sort-keys rule, but they autofix doesn't work in 1 iteration.
jsonc/sort-keys
For a particularly large JSON file, it takes hitting save many times before the file is finally in the order it needs to be in.
Here's a minimal-ish sample:
{ "i::b::c": "", "i::a::l": "", "i::d::h": "", "i::d::l": "", "i::ap::mwd": "", "i::b::cc": "", "a::c::h::c": "", "a::c::h::e": "", "i::b::caj": "", "i::b::cac": "", "i::ap::av::l": "", "i::ap::mw::la": "", "a::c::pc::u": "", "a::c::pe::u": "", "a::c::vfi::u": "" }
For the above file to be alphabetized, I have to hit save (which runs autofix) twice.
The text was updated successfully, but these errors were encountered:
That's a limitation of ESLint. If your code requires many fixes, you may need to run autofixes multiple times.
Sorry, something went wrong.
No branches or pull requests
I have very large translation files that should be alphabetized according to the
jsonc/sort-keys
rule, but they autofix doesn't work in 1 iteration.For a particularly large JSON file, it takes hitting save many times before the file is finally in the order it needs to be in.
Here's a minimal-ish sample:
For the above file to be alphabetized, I have to hit save (which runs autofix) twice.
jsonc--sort-keys.mov
The text was updated successfully, but these errors were encountered: