This is an old revision of the document!
WindsP
Coding practices
<note important> REVIEW THIS</note>
Naming conventions
JavaScript variables/functions: camelCase
Routes: kebab-case
Table names and attributes: snake_case
Routes: kebab-case for naming and “.dot.case”, type of file specification e.g.: (.service.js, .controller.js, .resource.js, .directive.js, .model.js. … )
Client
Creating "page" route:
Four files: xxxx.js – state description, xxxx.html/pug – template, .scss – page specific styling, .controller.js – controller.
Configure the state:
Creating modals:
Adding entity to the model:
Warnings:
CSS leaks from page specific stylings – use classes to constraint it to the desired elements.
Server
Other materials used in WindsP:
~~DIR:.:?cols=list;page;mdate&hdrs=Description;Date&ego&collapse&sort=description~~
— WindsPCode