Mlem
Mlem copied to clipboard
Refactor views
As discussed in Mlem Development we want to adopt a solid architecture in the application.
Although we have many ideas about how that will look and patterns we'd like to use, as a first step we should work our way through the application and tidy up the current code (specifically within our views) so that we have an understandable base to look over and help inform the next decisions we make regarding the architecture.
This will bring us a few benefits as we work through this task;
- We can each gain an understanding of the areas of the application we choose to refactor
- The scope of each task remains fairly small (eg, just refactor it, don't change what/how it works)
- Identify/discuss any issues in the current implementations
- Allow us to move between different areas of the code base more easily, as the format will become standardised
Each view we choose to refactor will be given it's own task and should (ideally) be a single PR.
Each PR should receive a review of both the code changes and a regression check before merging.