sstent/FitTrack_GarminSync
1
0
Fork 0
mirror of https://github.com/sstent/FitTrack_GarminSync.git synced 2026-04-04 20:13:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

feat: Implement Garmin sync, login improvements, and utility scripts

Browse Source
This commit is contained in:
sstent
2025-10-11 11:56:25 -07:00
parent 56a93cd8df
commit 3819e4f5e2
921 changed files with 2058 additions and 371 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
specs/003-loginimprovements-use-the/research.md Normal file
View File

@@ -0,0 +1,11 @@
# Research Findings for Garmin Login Improvements
## Phase 0: Outline & Research
### Client Authentication for Sync Operations
- **Decision**: The API client will not send an `Authorization` header for subsequent sync operations (e.g., `/api/sync/garmin/activities`).
- **Rationale**: The feature specification (`spec.md`) explicitly states that "the api caller should not need a cookie - all state should be global for the Garmin Sync service" and that the service operates as a single-user system, implicitly using the stored Garmin credentials after a successful `/api/garmin/login`. This clarifies the discrepancy with the `sync_garmin_activities.json` contract, which showed an `Authorization: Bearer <token>` header.
- **Alternatives considered**:
- Client sending an `APP_BEARER_TOKEN` (rejected as it contradicts the stateless client requirement).
- Client sending a session cookie (rejected as it contradicts the stateless client requirement).