Original Repository: https://github.com/MeteoSwiss/opendata-explorer
Relevant resources
- End-user flows dependent on OGD products
This project was generated using Angular CLI version 18.2.12.
To start a local development server, run:
ng serve
Once the server is running, open your browser and navigate to http://localhost:4200/
. The application will automatically reload whenever you modify any of the source files.
Angular CLI includes powerful code scaffolding tools. To generate a new component, run:
ng generate component component-name
For a complete list of available schematics (such as components
, directives
, or pipes
), run:
ng generate --help
To build the project run:
ng build
This will compile your project and store the build artifacts in the dist/
directory. By default, the production build optimizes your application for performance and speed.
To execute unit tests with the Karma test runner, use the following command:
ng test
For end-to-end (e2e) testing, run:
ng e2e
Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.
For more information on using the Angular CLI, including detailed command references, visit the Angular CLI Overview and Command Reference page.
Generally, we are orientating ourselves at the default Typescript naming conventions.
Whenever possible, a Github issue should be referenced in both branchname and commit message:
- Branches:
[feature|hotfix]/[xxx]-[name-of-branch]
, wherexxx
refers to a Github issue number and thename-of-branch
is a short summary of the feature/hotfix.` - Commits:
#[xxx] Your commit message
, , wherexxx
refers to a Github issue number
Our githooks check for both the branch name and the commit message, but they will only output a warning if they don't match. This is because there are times when you might want to deviate from these rules.