FRISTENKALENDER SPA

⚙️ Setting up development environment

Make sure you have the latest version of node installed (recommended via node version manager nvm).

$ npm install

$ npm run start # starts local dev server (including hot reload)
$ npm run lint # lints the whole project (eslint)
$ npm run format # formats the whole project (prettier)
$ npm run test # runs E2E tests (playwright) assuming the dev server is up and running

🏷️ Semantic commit messages

To meet the pull request title convention requirements enforced by Github Actions, here is a brief guide to help choosing the appropriate tag for each purpose:

• build: - changes that affect the build system or external dependencies
• chore: - miscellaneous commits and routine tasks
• ci: - changes to the CI/CD configuration
• docs: - updating the documentation
• feat: - adding or removing a feature feature
• fix: - bug fixes
• perf: - performance improvement
• refactor: - improve code structure, readability, or maintainability
• revert: - reverts a previous commit
• style: - code formatting and styling that do not affect functionality
• test: - adding or updating tests

🔐 Auth0 authentication

Note

During local development, authentication is currently not required. Instead, a dummy account [email protected] will be already logged in at both local dev server startup as well as build preview.

To get past the landing page when navigating through the staging environment https://fristenkalender.stage.hochfrequenz.de and production environment https://fristenkalender.hochfrequenz.de, users need to authenticate using their Hochfrequenz login credentials.

🔗 Links

Marktgut
Fristenkalender (legacy)
Mockup: TBD
Azure: TBD

fristenkalender-generator
fristenkalender-functions
fristenkalender-frontend-legacy