This project was created as a seed project and as example application for Angular starting with version 17.3.0.
Run npm run start
or npm run start:aot
for a dev server. Navigate to http://localhost:4200/
. The application will automatically reload if you change any of the source files.
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 build
or preferably npm run build:aot
to build the project. The build artifacts will be stored in the dist/
directory.
Run npm run test
to execute the unit tests via Karma.
Run ng e2e
to execute the end-to-end tests via a platform of your choice. To use this command, you need to first add a package that implements end-to-end testing capabilities.
To get more help on the Angular CLI use ng help
or go check out the Angular CLI Overview and Command Reference page.
- Lazy loading feature modules
- Module 1: retrieve and display data from API
- Module 2: state management
- HTTP interceptor to handle errors.
- Shared module.
- Integrated Material Design.
- Data model with Adapter.
- Eslint integrated.
- Commit rules with Husky.
- Mock local server for development and testing. (TODO)
- Unit testing. (TODO)
- E2E testing. (TODO)
- Responsive layout with Angular's BreakpointObserver Service. (TODO)
Use Gitflow Workflow for development.
Following the Angular Style Guide is strongly recommended.
Commit conventions allow team to add more semantic meaning to git history. This e.g. includes type, scope or breaking changes. With this additional information tools can derive useful human-readable information for releases of project. Some examples are angular commit rules
Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject:
type(scope?): subject
body?
footer?
git commit -m "docs: add developer docs"
git commit -m "docs(scope or developer.md or package name): add developer docs"
// To close issue
git commit -m "fix(button): fix button target event , closes #JIRANUMBER "
If the commit reverts a previous commit, it should begin with revert:, followed by the header of the reverted commit. In the body it should say: this reverts commit hash., where the hash is the SHA of the commit being reverted.
- chore: Change build process, tooling or dependencies.
- ci: Changes to our CI configuration files and scripts (example scopes: JenkinsFile, Build)
- feat: Adds a new feature.
- fix: Solves a bug.
- docs: Adds or alters documentation.
- style: Improves formatting, white-space.
- refactor: Rewrites code without feature, performance or bug changes.
- perf: Improves performance.
- test: Adds or modifies tests.
- revert: Changes that reverting other changes