Skip to content

/standard

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

curated-linter #742

Closed
mightyiam opened this issue Jan 10, 2017 · 1 comment

Comments

@mightyiam
Copy link
Contributor

commented Jan 10, 2017

Thank you so much for standard and standard-engine and the wonderful ecosystem that had evolved around them.

Having read through the code for standard-engine and contemplated the API for several hours, I have spent more than a day coming up with an initial readme for an alternative. It is called curated-linter and it lives here: https://github.com/mightyiam/curated-linter.

Although not written in the readme, I have intention for it to be able to provide the users of linters produced by standard-engine full compatibility, with deprecation warnings. Off the top of my head the incompatibilites are the format of the user's package.json configuration property feature and also the signature of the lintFiles and lintText. There are probably more.
@feross

This comment has been minimized.

Sign in to view
Copy link
Member

commented Jan 13, 2017

So this is basically a fancy version of standard-engine? Neat.

@mightyiam mightyiam closed this Jan 13, 2017

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
2 participants
@mightyiam @feross
You can’t perform that action at this time.