Initial Commit

This commit is contained in:
Eric Gullickson
2025-09-17 16:09:15 -05:00
parent 0cdb9803de
commit a052040e3a
373 changed files with 437090 additions and 6773 deletions

View File

@@ -1,14 +1,13 @@
# Ustations Feature Capsule
# Stations Feature Capsule
## Quick Summary (50 tokens)
[AI: Complete feature description, main operations, dependencies, caching strategy]
## Summary
Search nearby gas stations via Google Maps and manage users' saved stations.
## API Endpoints
- GET /api/stations - List all stations
- GET /api/stations/:id - Get specific lUstations
- POST /api/stations - Create new lUstations
- PUT /api/stations/:id - Update lUstations
- DELETE /api/stations/:id - Delete lUstations
## API Endpoints (JWT required)
- `POST /api/stations/search` — Search nearby stations
- `POST /api/stations/save` — Save a station to user's favorites
- `GET /api/stations/saved` — List saved stations for the user
- `DELETE /api/stations/saved/:placeId` — Remove a saved station
## Structure
- **api/** - HTTP endpoints, routes, validators
@@ -22,7 +21,7 @@
## Dependencies
- Internal: core/auth, core/cache
- External: [List any external APIs]
- External: Google Maps API (Places)
- Database: stations table
## Quick Commands
@@ -33,3 +32,9 @@ npm test -- features/stations
# Run feature migrations
npm run migrate:feature stations
```
## Clarifications Needed
- Search payload structure (required fields, radius/filters)?
- Saved station schema and required fields?
- Caching policy for searches (TTL, cache keys)?
- Rate limits or quotas for Google Maps calls?