luckberg/familysync
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(13-02): complete ESLint violation elimination plan

Browse Source
This commit is contained in:
Lucas Berger
2026-06-11 20:25:47 -04:00
parent 03e953158a
commit 1453cbed76
3 changed files with 201 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.planning/ROADMAP.md
+3 -3
View File
@@ -226,7 +226,7 @@ Make FamilySync configurable, administrable, and maintainable for real multi-mem
**Wave 2** *(blocked on Wave 1 completion)*
- [ ] 13-02-PLAN.md — Fix all first-run lint violations across both apps, green `pnpm lint` (D-13-05/06)
- [x] 13-02-PLAN.md — Fix all first-run lint violations across both apps, green `pnpm lint` (D-13-05/06)
**Wave 3** *(blocked on Wave 2 completion)*
@@ -248,7 +248,7 @@ Make FamilySync configurable, administrable, and maintainable for real multi-mem
| 10. Admin Role & Settings | v1.1 | 0/? | Not started | - |
| 11. Per-Event Reminders | v1.1 | 0/? | Not started | - |
| 12. Initial Setup Wizard | v1.1 | 0/? | Not started | - |
| 13. Real Lint Gate (ESLint) | v1.1 | 0/3 | Not started | - |
| 13. Real Lint Gate (ESLint) | v1.1 | 2/3 | In Progress| |
## Backlog
@@ -256,7 +256,7 @@ Make FamilySync configurable, administrable, and maintainable for real multi-mem
**Goal:** [Captured for future planning] Abstract the calendar backend behind a provider interface so Fastmail/CalDAV is one implementation among potentially many. Shipping with a single provider is fine, but the broker, sync, and event-expansion layers should be structured so additional providers (e.g. other CalDAV hosts, Google Calendar, generic ICS feeds) can be added without rework. Captures the "provider" seam as an explicit architectural concern.
**Requirements:** TBD
**Plans:** 3/4 plans executed
**Plans:** 2/3 plans executed
Plans: