Skip to content

Housekeeping After Multi-Tenancy Features are Implemented #202

@DanielElisenberg

Description

@DanielElisenberg

Housekeeping After Multi-Tenancy Features are Implemented

The code has changed quite a bit with the new features. Do some general housekeeping as the codebase is starting to show its age, and the fact that it has gone through multiple iterations.

Filesystem

All adapters should be based on a protocol and the tests should be structured in a way where we can mock these protocols if needed.
The tests themselves should also be updated to better reflect the changes to the structure of the code after the multi tenancy changes. Make sure to also clean up the test resources. A lot of the code, especially the tests and test resources are starting to show signs of having gone through refactors and should undergo some housekeeping to be more approachable and readable.

Testing

The test resources should be structured better and tests should be less reliant on each other. Restructure the test directory to match the new structure of the app.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions