Fix/suppress current eslint warnings #1936
Merged
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 also raises
import/no-unresolved
andimport/extensions
to error leveleverywhere except
docs
.I didn't touch the warning about lacking tests for
addons/notes
so that it keeps reminding that they still have to be written.It would be nice if we could find a way to know if some new warnings are introduced with a PR (like it's done with code coverage). Does anyone know how to get this metric from CircleCI?