##Project Description The frontend application for our scheduler app, connecting via api to the backend application for data storage.
###Setup: Install node, then run:
$ npm install && bower install
$ npm install -g webdriver-manager #for selenium testing
$ webdriver-manager update --standalone
###Run Server:
$ gulp #development mode
$ gulp --production #production mode
###Build files only:
$ gulp --build #builds dev environment
$ gulp --production --build #builds production enviornment
###Test Build: ####Run unit tests:
$ gulp unit #runs all unit tests
####Run e2e tests: In one terminal
$ gulp
In second terminal
$ gulp e2e
In third terminal
$ webdriver-manager start
###Workflow
- Pull remote changes - Use naming convention feature/ for creating feature branches, chore/ for chores
- Do development in feature branch
- Push the feature branch to github (git push origin feature/)
- Make a Pull request to merge back into development branch.
###Coding Style:
- "Make everything as simple as possible, but not simpler."
- Try to stay consistent in coding styles
- Use 2 spaces for tabbing
- Align characters when possible.
- Naming conventions: - Modules: lowerCamelCase - Controllers: UpperCamelCase (eg: "MainController") - Directives: lowerCamel Case - Services: UpperCamelCase (singular)
- Comment about WHAT your code does, not HOW.