Suggestion: Static analysis / Adopting explicit rules for code style

[mthh]

This is just a suggestion but by Bertin v2 you could add explicit rules about code style (number of spaces for indent, location of brackets after an if/for, location of comments, etc.) and add static code analysis with something like ESLint.

ESLint helps identify problematic or confusing code patterns (see for example here) and helps to enforce a chosen code style. It integrates with most code editors (and is used by many projects) so problems can be seen when writing code.

This would help to guarantee the homogeneity of the code base (style of the code, development pattern used, etc.) especially for contributors who submit code through pull requests.

[neocarto]

Sounds good.