Add support for other standard linters - RM always on req for 'standard' #92
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.
@timoxley For the record.... I'm a standard fella. But my boss... He loves the semicolons. So here we are.
I could not use standard-loader as is because of the always on requirement of standard up top. Our system dictates linting rules based on the standard version it finds and if standard is included in the app semistandard will never get hit.
By moving this require down to after the config.standard examination, those not using standard standard 😭will no longer be required to have it installed to use the loader.
Can I get that merged up soon or feedbacked trying to put a lid on this build by EOW. Purrty Please and thank you.