Backend technical debt

[AndyRae]

Is there an existing issue for this?

• [X] I have searched the existing issues

Is your proposal related to a problem or functionality gap?

In development we've identified a few issues that would make the backend much easier to develop, maintain, and faster for users.

Here are some ideas - I'm very open to opinions on any of them, and always looking for more as well.

Describe your proposal

• [x] #685

  • [x] ScanReportListView
  • [x] StructuralMappingTableListView
  • [x] (double check for any more!) (Views that get data by the API, but are duplicating calls, as the rendered data is all driven by the API. Remove the code that does this)

• [x] #684

  • [x] rename the app/api/api project to app/api/core or config (as it being API is just confusing)
  • [x] create a new app/api/api app, move all api relevant code in there.
  • [x] Retain the mapping app for Django views, and general mapping application logic. (Using Django projects to provide this separation)

• [x] #699

  • [x] Turn off the ProcessQueue, delete the function
  • [x] Delete temp code to switch between the two by UPLOAD_ONLY environment variable.

• [ ] #726

• [x] Delete commented out code, document functions, add types, remove unused code.

• [x] Add MyPy type checker gradually

• [ ] A new "version" endpoint

• [x] #741

  • [x] Remove production from the existing CI/CD
  • [x] Remove test from behind a user gate.
  • [x] Enable deploy to dev run from workflow_dispatch so we can deploy any branch there for deployed testing.
  • [x] Add a Next.js build check on raise PR

Describe alternatives you've considered

No response

I'm part of a Project Team

Yes - DRS

Anything else?

No response

Are you willing to contribute to developing this feature?

✅ Yes, me or my team intend to do the development.