Gino Miceli
Gino Miceli
All components should ideally use Material theming; specific instances of color attributes can be removed. https://material.io/develop/android/theming/color
We could then remove the need to group mutations by `User`, and would not need to pass around the `User` to all mutation methods.
Currently this is done in the background worker by the currently logged in user.
`Date` is mutable and isn't thread-safe. Since we only use `Date` for timestamps, these can be replaced with simple longs.
These should be observed by views which update state accordingly. @dturner as per our discussion.
Colors that don't look quite right - [ ] Toolbar background and nav icon - [ ] Surface container color, e.g., survey list backround
We should have notifications for these background operations: - [ ] New LOIs added to a job by organizer - [ ] New jobs added to a survey by organizer...
Room `@Transaction` annotation makes this easy. This will prevent failed operations from leaving the db in an invalid state.
Ideas: * We currently split the project config into many different tables, even though the entire hierarchy is always read and written as a single unit. We could reduce complexity...
- [x] Automated testing run via CI - [x] Automated UI testing run via CI - [ ] Acceptable unit test coverage - [ ] Acceptable UI test coverage