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
One of the hazards Agoric left out of Jessie is automatic semicolon insertion.
I'd appreciate it if we could avoid that hazard in this repo; my editors make lots of noise on every line with a missing semicolon at the end.
I tend to follow their style; it's based on airbnb style; the details are in https://github.com/Agoric/new-repo .
The text was updated successfully, but these errors were encountered:
I don't think semicolon is problematic as before. With the use of linters and preprocessors for JS the danger part is eliminated. https://standardjs.com/rules.html#semicolons
I follow JavaScript Standard Style which has support for VSCode and also other editors. https://standardjs.com/#are-there-text-editor-plugins
Sorry, something went wrong.
OK, using Standard Style does seem to address the ASI hazard.
I thought about closing this now, but I prefer to leave it open until a CI check enforces this style on master.
If you prefer to close this now, I don't mind if you go ahead.
No branches or pull requests
One of the hazards Agoric left out of Jessie is automatic semicolon insertion.
I'd appreciate it if we could avoid that hazard in this repo; my editors make lots of noise on every line with a missing semicolon at the end.
I tend to follow their style; it's based on airbnb style; the details are in https://github.com/Agoric/new-repo .
The text was updated successfully, but these errors were encountered: