-
-
Notifications
You must be signed in to change notification settings - Fork 880
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
Formalize code styles #818
Comments
Where would we put this information optimally?
|
See also: #806 - Naming policy for boolean options |
Perhaps both places? |
When docs are written in two places decoupled from each other, one will fast get outdated and ignored. I would like to have one source of truth. |
Started a G-Docs: https://docs.google.com/document/d/1rOevJnJcUi5wmjS1ZWMjmsQME9w5pj94oFriFH-9Fq0/edit# |
Maybe we could generate/include the docs page from the |
|
The jsdocs part will be handled here: #1397 |
What is missing for this issue to be considered "done"? Most of our code styles are enforced by |
I agree this is too generic to be useful and should be closed |
Clear and concise description of the problem
Currently it is not clear how some features should be implemented.
Suggested solution
It would be nice if there was a document that explains the code styles/guidelines.
Alternative
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: