Add documentation for overriding configuration settings #57
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.
In yesterdays frontend open space, we had a discussion about ESLint configuration. As a result, I have agreed to review and update or enhance our frontend playbook and the eslint-config-springernature documentation.
Among other details, we discussed the configuration setting for specific ECMAScript versions. This repository uses ECMAScript 6 in the ESLint configuration, which might be outdated for actual projects that import eslint-config-springernature. This is even more of a concern when it's used in a completely new project, that would want to use more modern versions of ECMAScript.
I added new sections and changed an existing headline with the intention of giving developers more confidence in their ESLint configuration.
Please have a look and add your comments and changes.