Eslint warnings support #1671
Draft
Eslint warnings support #1671
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.
馃幆 Goal
To add support for eslint-generated smells.
馃摑 Details
This PR actually just updates dependencies on
mumuki-domain, so that it incorporates newMumukit::Inspectionextensions for the JS language. All the real work actually occurs in that gem and the runner itself.Currently, only support for missing semicolons was included.
馃摳 Screenshots
馃敊 Backwards compatibility
100%
馃敎 Future work
We may add more eslint-based warnings in the runner without having to actually change anything here.