Separate bootstrap settings from runtime overrides with a dedicated runtime settings manager
This commit is contained in:
@@ -41,6 +41,7 @@ Reference: `Docs/Refactoring.md` for full analysis of each issue.
|
||||
- Issue: `POST /api/setup` mutates `app.state.settings`, and startup logic also replaces `app.state.settings` with persisted runtime overrides, mixing immutable startup settings with mutable runtime config.
|
||||
- Propose: Introduce a runtime settings manager or configuration service that resolves effective settings from persisted overrides without mutating the startup settings object on `app.state`.
|
||||
- Test: Validate the setup flow persists runtime settings in the database and that runtime settings are resolved through the new manager instead of direct `app.state.settings` mutation.
|
||||
- Status: completed
|
||||
|
||||
6. Introduce explicit service and repository abstractions for swapability and testing
|
||||
- Goal: Reduce tight coupling and improve replacement/testing of core backend components.
|
||||
|
||||
Reference in New Issue
Block a user