Fixes the hardcoded django content_type ids used in the backend, client, and workers.
This enables the app to be deployed fully working.
The approach has been to make the backend to be responsible for the content_type, and not trust the client, in two ways:
When a ScanReportConcept is created through the API (when used by the workers, or the frontend), the content type is passed as a string, this is then used to lookup the content type ID.
When a content_type is used for frontend logic, mostly for rendering / filtering, a new API endpoint has been created to get the content type ID.
Closes #637
Closes #641
Large diffs in the Javascript are Prettier working away.
Checks
Important: please complete these before merging.
[x] Run migrations, if any.
[x] Update changelog.md, including migration instructions if any.
Changes
Fixes the hardcoded django
content_typeids used in the backend, client, and workers.This enables the app to be deployed fully working.
The approach has been to make the backend to be responsible for the
content_type, and not trust the client, in two ways:ScanReportConceptis created through the API (when used by the workers, or the frontend), the content type is passed as a string, this is then used to lookup the content type ID.content_typeis used for frontend logic, mostly for rendering / filtering, a new API endpoint has been created to get the content type ID.Closes #637 Closes #641
Large diffs in the Javascript are Prettier working away.
Checks
Important: please complete these before merging.
changelog.md, including migration instructions if any.