Convention de nommage
- valeur constante -> CONSTANT_VALUE
- variable /function -> myFunction, myValue
- classe -> MyComponent

https://google.github.io/styleguide/jsguide.html#naming
Give as descriptive a name as possible, within reason. Do not worry about saving horizontal space as it is far more important to make your code immediately understandable by a new reader. Do not use abbreviations that are ambiguous or unfamiliar to readers outside your project, and do not abbreviate by deleting letters within a word.
Écrire pour les autres devs et pas pour la machine
Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live. Code for readability.
https://github.com/airbnb/javascript/tree/master/react#naming
(eslint-plugin-react)

https://eslint.org/docs/rules/id-blacklist

Éviter les noms trop génériques / non sémantiques
Actions à prendre
- Prendre un peu de temps pour lire/relire les guides google et airbnb : https://google.github.io/styleguide/jsguide.html et https://github.com/airbnb/javascript/tree/master/react
- Rédiger dans un .md le rappel de quelques règles et les liens vers les guides
- Implémenter la règle ESLint
deck
By Alexandre BARBIER
deck
- 316