-
-
Notifications
You must be signed in to change notification settings - Fork 105
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
Style guidelines #79
Comments
From my point of view this is ok. What are the risks? Is it possible that some parts are not working then or is it just the style-formating of the code? |
Most of the rules can be automatically fixed (and there's a very simple option to autofix everything). Some things cannot and would be highlight and need manually fixing (not too difficult) |
If we did our best to use conventional commit style that'd be a great help to future releases as changelogs could then be automatically generated. There are many tools for enforcing/suggesting this and also for making writing these commits as easy as possible. |
Should we apply commitlint using https://www.npmjs.com/package/husky? |
See materializecss#79. Also bump version in package-lock
See materializecss#79. Also bump version in package-lock
The issue is about code style, not just commit style, I don't think it can be closed yet. |
See materializecss#79. Also bump version in package-lock
Can we close it now? The conventional commit style is now enforced via Husky. Please confirm and/or close. |
As said in the comment above, this original issue is about enforcing the code style (indentation, etc.), not only the commit message format. |
Ah sorry, my misktake. Didnt read properly. As far as i remember, there was a automatic code styling applied though, when i was writing some changes. Maybe it was serverside at CI Level. |
Hello @ChildishGiant PS: Where are you all? 😆 Hope you all are doing fine and thank you all for starting Materialize. |
Currently the project has a basic .eslintrc set up but I think it'd make contributing easier and more consistent if we opted to use js standard style. Many projects (including npm, GitHub and the UK government) use this style
The text was updated successfully, but these errors were encountered: