-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Including JS linting in the Solidus workflow #2849
Comments
👍 Repeating my comment from #2847
|
From what I've seen, the AirBnB JS style guide seems to be pretty well received. Not saying we have to follow it exactly, just like we have exceptions in our Rubocop linter, but may be a good start. |
I agree, but @tvdeyen makes a great point about adopting it incrementally. |
@ericsaupe @tvdeyen I've been using the AirBNB style guide for JS and React on projects outside of Solidus when no better alternative is already provided. I've found it to be pretty sensible in most cases though some devs have argued to relax certain points. I think its important to stress the importance of using good tooling to make working with ESLint pain free. For example both VS.code and Webstorm have very good plugins that automate working with ESLint, maybe even make it fun....So lets make sure we mention tooling in the docs. |
I use the AirBnB lint rules as well. But we need to relax even more, because our current code will violate it all the time. 👍 for strong tooling. We still need to ensure to not scare contributors |
I'm also 👍 with what has been proposed by @tvdeyen in #2849 (comment). AirBnB rules (more relaxed) are fine but that's the goal we should strive step by step as proposed. |
Yes, I think we are fine now, thanks @seand7565! |
After making #2847 and hearing @tvdeyen's feedback, I feel like we need to adopt some JS standards for Solidus.
Solidus isn't a JS project; it doesn't seem like this is something we should obsess over. However the project relies on having a functioning admin UI, so it's pragmatic to make sure we have high code quality when it comes to JS.
I'm not sure what the best solution for Solidus is (and don't want to start an argument), but I think it's worth discussing with other contributors. Thoughts?
The text was updated successfully, but these errors were encountered: