Code quality guidelines¶
Status
Whole page reflects both branches.
A few guides onto how code contributed to Sokora should look like.
- Use
camelCasefor both variables and function names. UseCONST_CASEfor constant values that are shared, exported or not. - Use early returns to avoid nesting.
- Avoid non-nullish assertions, they are valid only when absolutely needed.
- Really try not to use ignore comments. The linter is (almost) always right.
- Prefer, when possible,
Promise.allover having severalawaitstatements.
There's not a deep style guide since the ql task should be able to handle everything on its own.