Document task DB access and unify background task DB handling
This commit is contained in:
@@ -406,4 +406,6 @@ Reference: `Docs/Refactoring.md` for full analysis of each issue.
|
||||
|
||||
**Docs changes needed:** Add a "Background Tasks and Database Access" section to `Docs/Architekture.md` explaining why tasks own their connections and how to write a new task.
|
||||
|
||||
**Status:** Completed ✅
|
||||
|
||||
**Why this is needed:** Without explanation, the inconsistency between router DI-provided connections and task-managed connections looks like an oversight. Documentation prevents future developers from incorrectly trying to inject a DB connection into a task via `Depends`, which would fail silently at runtime.
|
||||
|
||||
Reference in New Issue
Block a user