Frontend

Development workflow

Commit message convention

We follow the conventional commits specification (opens in a new tab) for our commit messages:

• fix: bug fixes, e.g. fix crash due to deprecated method.
• feat: new features, e.g. add new method to the module.
• refactor: code refactor, e.g. migrate from class components to hooks.
• docs: changes into documentation, e.g. add usage example for the module..
• test: adding or updating tests, eg add integration tests using detox.
• chore: tooling changes, e.g. change CI config.

Our pre-commit hooks verify that your commit message matches this format when committing.

Linting and tests

ESLint (opens in a new tab), Prettier (opens in a new tab), TypeScript (opens in a new tab)

We use TypeScript (opens in a new tab) for type checking, ESLint (opens in a new tab) with Prettier (opens in a new tab) for linting and formatting the code, and Jest (opens in a new tab) for testing.

Our pre-commit hooks verify that the linter and tests pass when committing.