Overview

Links to jira tickets

Updates after initial repo commit.
Working code foundation for the taxonomy repo. Functional db/api/app code + deployments + docker + tests.

A list of items that are good to consider when making any changes.

Note: this list is not exhaustive, and not all items are always applicable.

[ ] New files/classes/functions have appropriately descriptive names and comment blocks to describe their use/behaviour
[ ] I have avoided duplicating code when possible, moving re-usable pieces into functions
[ ] I have avoided hard-coding values where possible and moved any re-usable constants to a constants file
[ ] My code is as flat as possible (avoids deeply nested if/else blocks, promise chains, etc)
[ ] My code changes account for null/undefined values and handle errors appropriately
[ ] My code uses types/interfaces to help describe values/parameters/etc, help ensure type safety, and improve readability

[ ] I have commented my code sufficiently, such that an unfamiliar developer could understand my code
[ ] I have added/updated README's and related documentation, as needed

[ ] I have added/updated unit tests for any code I've added/updated
[ ] I have added/updated the Postman requests/tests to account for any API endpoints I've added/updated

[x] I have run the linter and fixed any issues, as needed
See the lint commands in package.json
[x] I have run the formatter and fixed any issues, as needed
See the format commands in package.json

[ ] I have addressed all SonarCloud Bugs, Vulnerabilities, Security Hotspots, and Code Smells

Please describe the tests that you ran to verify your changes.

Please add any relevant UI screenshots, if applicable.