dev environment: Add npm run fix
to fix (some) esLint errors
#7337
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.
This is the most helpful command I have figured out so far.
Let me know if there is a better way to fix formatting errors, e.g. an auto-formatting tool you use. Currently, I do "Format Document" in VS Code that results in a different style of formatting (semicolons everywhere), and then I run
npm run fix
to change it to this project's style.(In case you are curious, I'm trying to refactor the version selector code slightly so that we can have some unit tests, and thus more confidence when improving the "stay on the same page when switching versions" behavior. There is a draft in #7338 )