This project was generated with Angular CLI. Rather than installing Angular's CLI globally, you can invoke commands on OSMT's ng devDependency by calling npm run ng whatever_command. This may help avoid conflicts with other Angular tooling installed on your development machine.
Run npm run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.
Run npm run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.
Run npm run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.
Run npm run ng test to execute the unit tests via Karma. Use <ctrl + c> to exit.
A whitelabel JSON file's URI can be defined in the environment file for deployment. This file is loaded dynamically at runtime and can be replaced
without rebuilding with access to the deployed file. The URI can be set for each angular environment by setting environment.whiteLabelConfigUri.
On app launch, the file is downloaded in an api call and is deserialized into the AppConfig property AppConfig.settings which is available globally.
If any changes to the signatures need to be made, such as adding new properties, then both the interface and class located in
src/app/models/app-config.model.ts must be updated.
- The interface IAppConfig provides the expected shape of the json files and type safety when parsing config JSON.
- The class DefaultAppConfig defines our default set of configurations when no overriding URI is provided.
To get more help on the Angular CLI use ng help or go check out the Angular CLI README.