Refactor geo re-resolve to use geo_cache repo and move data-access out of router
This commit is contained in:
@@ -16,7 +16,9 @@ This document breaks the entire BanGUI project into development stages, ordered
|
||||
|
||||
---
|
||||
|
||||
#### TASK B-1 — Create a `fail2ban_db` repository for direct fail2ban database queries
|
||||
#### TASK B-1 — Create a `fail2ban_db` repository for direct fail2ban database queries ✅
|
||||
|
||||
**Status:** Completed
|
||||
|
||||
**Violated rule:** Refactoring.md §2.2 — Services must not perform direct `aiosqlite` calls; go through a repository.
|
||||
|
||||
@@ -41,6 +43,8 @@ This document breaks the entire BanGUI project into development stages, ordered
|
||||
|
||||
#### TASK B-2 — Remove direct SQL query from `routers/geo.py`
|
||||
|
||||
**Status:** Completed ✅
|
||||
|
||||
**Violated rule:** Refactoring.md §2.1 — Routers must contain zero business logic; no SQL or repository imports.
|
||||
|
||||
**Files affected:**
|
||||
|
||||
Reference in New Issue
Block a user