We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
No description provided.
The text was updated successfully, but these errors were encountered:
I think that a complete coding convention is too much regarding the size of the project.
Let's code:
The linter can be used to fix all the "tab vs spaces" or " bracket before or after newline" debates.
Sorry, something went wrong.
The hard part is too make the dev start. And a strict coding convention might not help in that matter
Sorry for my late answer...
I agree that a coding convention will be too much for this project, this is why I wrote only naming conventions and some basics about the techs used.
I need to add some commands in package.json so it will lint and fix automatically on commits. So it will be painless for everyone.
package.json
No branches or pull requests
No description provided.
The text was updated successfully, but these errors were encountered: