-
Notifications
You must be signed in to change notification settings - Fork 18
Discussion: consolidating a linter within the project #327
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
Comments
Thanks for opening this discussion - it's definitely overdue to bring all the linter/style conversations into one place. I'm happy to help push this forward, and if there's interest, I'm also willing to take the lead on coordinating the effort. That includes drafting a proposed shared config, documenting migration steps and helping apply it consistently across repos. Totally open to collaborating with others on this as well - just want to help get us to a place where we have consistent and maintainable linting across the three orgs. |
Next step: Schedule a working session to discuss. Specifically to include meta topic of "global tooling", the eslint options, and maybe |
I’m opening this discussion to consolidate in one place the conversation about the linter, as there have been discussions about code style spread across different packages
Some places where there has been discussion or an attempt to update or change standard/eslint:
semistandard
serve-static#171neostandard
/eslint-config-express
serve-static#172The text was updated successfully, but these errors were encountered: