Update frontend guidelines for ESLint and prettier #3691
Merged
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
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 could not find any guidelines on updating the documentation, so I'll try to update any outdated parts when I stumble upon them and feel comfortable that the update is correct and relevant.
The PR contains very minor changes to the frontend guidelines. It currently recommends using JSLint, which produces a rather large amount of warnings/errors,
which can be confusing to someone new to the project (e.g., me 😳 ).
ESLint/Prettier is the current default create-react-app approach.
As always, add/remove/change/discard/comment on this PR, whichever suits best.