mirror of
https://github.com/pacnpal/thrillwiki_django_no_react.git
synced 2025-12-21 17:31:08 -05:00
1b246eeaa4
- Implement tests for RideLocation and CompanyHeadquarters models to verify functionality and data integrity. - Create a manual trigger test script for trending content calculation endpoint, including authentication and unauthorized access tests. - Develop a manufacturer sync test to ensure ride manufacturers are correctly associated with ride models. - Add tests for ParkLocation model, including coordinate setting and distance calculations between parks. - Implement a RoadTripService test suite covering geocoding, route calculation, park discovery, and error handling. - Create a unified map service test script to validate map functionality, API endpoints, and performance metrics.
101 lines
3.5 KiB
Markdown
101 lines
3.5 KiB
Markdown
# 🔄 CONTINUE WORK PROMPT
|
|
|
|
**Use this prompt to continue working on the ThrillWiki Nuxt frontend implementation.**
|
|
|
|
---
|
|
|
|
## PROMPT FOR CONTINUING WORK
|
|
|
|
```
|
|
I need to continue working on the ThrillWiki Nuxt frontend implementation. This is an ongoing project with existing work and documentation.
|
|
|
|
CONTEXT:
|
|
- Working directory: /Users/talor/thrillwiki_django_no_react
|
|
- Django backend exists at backend/ with REST API at /api/v1/
|
|
- Nuxt frontend being built in frontend/ directory
|
|
- Comprehensive planning documentation exists at docs/nuxt/
|
|
- Project uses Context7 for documentation and existing component library
|
|
|
|
CRITICAL: READ THESE FILES FIRST (IN ORDER):
|
|
1. docs/nuxt/00-PROJECT-STATUS.md - Current status and immediate next steps
|
|
2. docs/nuxt/00-CONTEXT-SUMMARY.md - Complete project context and decisions
|
|
3. docs/nuxt/00-CONTINUATION-GUIDE.md - How to continue work and common issues
|
|
4. docs/nuxt/IMPLEMENTATION-READY.md - Complete plan summary
|
|
|
|
CURRENT STATE ASSESSMENT:
|
|
- Check the "Current Phase" in 00-PROJECT-STATUS.md
|
|
- Look for any "BLOCKER" or "IN PROGRESS" items
|
|
- Review the "IMMEDIATE NEXT STEPS" section
|
|
- Check if frontend/ directory exists and what's implemented
|
|
|
|
IMPLEMENTATION PHASES:
|
|
- Phase 1: Foundation (Nuxt setup, auth, basic components)
|
|
- Phase 2: Core Features (parks, rides, search, photos)
|
|
- Phase 3: Advanced Features (submission, moderation, maps)
|
|
- Phase 4: Polish & Deployment (testing, optimization, deployment)
|
|
|
|
TECHNICAL STACK (FINALIZED):
|
|
- Nuxt 3 with Vue 3 Composition API + TypeScript
|
|
- Pinia for state management
|
|
- JWT authentication with refresh tokens
|
|
- Component library: [Check architecture-decisions.md for choice]
|
|
- Custom composables with $fetch for API integration
|
|
|
|
COMMON CONTINUATION SCENARIOS:
|
|
|
|
IF FRONTEND DIRECTORY DOESN'T EXIST:
|
|
- Component library choice may be needed
|
|
- Follow Phase 1 setup instructions
|
|
- Initialize Nuxt 3 project structure
|
|
|
|
IF FRONTEND EXISTS BUT INCOMPLETE:
|
|
- Check package.json for installed dependencies
|
|
- Review current implementation status
|
|
- Continue with next phase tasks
|
|
|
|
IF BLOCKED:
|
|
- Check 00-PROJECT-STATUS.md for blocker details
|
|
- Review 00-CONTINUATION-GUIDE.md for solutions
|
|
- Update status documentation with progress
|
|
|
|
DEVELOPMENT WORKFLOW:
|
|
1. Update 00-PROJECT-STATUS.md with current progress
|
|
2. Follow implementation guides in docs/nuxt/implementation/
|
|
3. Test integration with Django backend at localhost:8000
|
|
4. Document decisions and progress as you work
|
|
5. Update status before ending session
|
|
|
|
KEY COMMANDS:
|
|
- Start Django: cd backend && uv run manage.py runserver
|
|
- Start Nuxt: cd frontend && npm run dev
|
|
- Test API: curl http://localhost:8000/api/v1/health/
|
|
|
|
Please start by reading the status files to understand the current state, then continue with the appropriate next steps based on the current phase and any blockers.
|
|
```
|
|
|
|
---
|
|
|
|
## QUICK REFERENCE FOR CONTINUATION
|
|
|
|
### If Starting Fresh (No frontend/ directory):
|
|
1. Read planning docs
|
|
2. Ask for component library choice if not decided
|
|
3. Run Phase 1 setup commands
|
|
4. Begin authentication implementation
|
|
|
|
### If Continuing Existing Work:
|
|
1. Check 00-PROJECT-STATUS.md for current phase
|
|
2. Review what's implemented in frontend/
|
|
3. Continue with next tasks in current phase
|
|
4. Update documentation as you progress
|
|
|
|
### If Encountering Issues:
|
|
1. Check 00-CONTINUATION-GUIDE.md for common solutions
|
|
2. Review architecture-decisions.md for technical context
|
|
3. Update 00-PROJECT-STATUS.md with blocker details
|
|
4. Document workarounds or solutions found
|
|
|
|
---
|
|
|
|
**Copy the above prompt to continue work on the ThrillWiki Nuxt frontend.**
|