... | ... | @@ -18,13 +18,16 @@ We're trying to follow the [official Angular 2 styleguide](https://angular.io/st |
|
|
* flat directories structure: components, directives, data store models, pipes, services
|
|
|
* components directory: most of our apps are centered on routes, so those are the primary component directories in the parent components directory, accompanied by a shared components directory for things like nav, footer, card, dropdown, modal, etc
|
|
|
* module barrels: index.ts files used to group similar exports (This is the [Node](https://nodejs.org/api/modules.html#modules_folders_as_modules) way, and [recommended](https://angular.io/styleguide#!#04-10) by Angular. This makes imports cleaner, dryer, and more maintainable)
|
|
|
* api config: to change your backend api url, look for api.config.ts next to api.service.ts in the services directory
|
|
|
|
|
|
## API config
|
|
|
To change your backend api url, look for api.config.ts next to api.service.ts in the services directory
|
|
|
|
|
|
## Style Guides and Best Practice
|
|
|
We maintain a [list of recommended styles guides](toolbox). Please take time to refer to them often. When working so fluidly between teams and projects, consistent style greatly enhances our efficiency and product quality.
|
|
|
|
|
|
|
|
|
### TODO
|
|
|
- add suggested styleguides? https://google.github.io/styleguide/javascriptguide.xml, https://github.com/airbnb/javascript, https://google.github.io/styleguide/htmlcssguide.xml, http://codeguide.co/
|
|
|
- js data error handling
|
|
|
- js data error handling?
|
|
|
- ng2-bootstrap (best we have, for now):
|
|
|
- modal service (or shared component???)
|
|
|
- alerts -> toasts
|
... | ... | |