Best Practice Guidelines
Describes what we expect from new code. Also includes special tips to help you getting started!
- Don't commit
package-lock.jsonif you're not making any changes to the libraries.
- If the issue you're working on require changes in both API and Frontend, give your Git branches the same name. CI will automatically pull the correct API's branch when testing the Frontend.
- We love screenshots - or better: screencasts. Include some in your pull requests to demonstrate your changes and you will have our eternal gratitude.
- Update the language files
npm run build:langsand commit them to reflect the changes
- We're getting rid of
material-ui. Please don't use them for new developments.