This repository has been archived by the owner on Jul 27, 2023. It is now read-only.
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 PR adds the ability to run a summary on all javascript files from the project and display the number of warnings either grouped by
filename
or bywarning
(type).I've also included a summary per file where you can see the number of warnings you have on a certain JS/JSX.
It's a very similar output to what Rubocop does with the
offenses
formatter (http://rubocop.readthedocs.io/en/latest/formatters/#offense-count-formatter).I think it's a good way of having a glimpse on what to focus on first, when getting your hands on a bigger project.
Here are a few sample outputs of the commands:
Full summary examples (by
filename
andwarning
)File summary (by default for
application.js
)