WindsPT@U.PORTO

windscanner.eu & NEWA

User Tools

Site Tools


windsp:index

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:
    • Permitions in with “permissions” and

Creating modals:

Adding entity to the model:

  • components/api/xxxx/xxxx.resource.js – middleware to connect with the server API.
  • components/api/xxxx/xxxx.service.js – auxiliar functions to handle this type of model data, these functions produce no side effects.

Warnings:

  • CSS leaks from page specific stylings – use classes to constraint it to the desired elements.

Server

  • Dashboard: GIT, Trello, Slack, …
  • Vagrant:

Other materials used in WindsP:

~~DIR:.:?cols=list;page;mdate&hdrs=Description;Date&ego&collapse&sort=description~~


WindsPCode

windsp/index.1499698216.txt.gz · Last modified: 2017/07/10 16:50 by Daniel Gomes