Repository navigation
Added landing page, sign up/log in, page links and backend connection - #27
Conversation
- Fetch individual trips from the backend when VITE_API_URL is configured - Adapt API responses to the frontend TripDetail model - Display newly created trips with an empty photo gallery - Show the 404 page for nonexistent trips - Preserve error handling for network and server failures - Add regression tests for trip loading and not-found handling - Update source-map-js from 1.2.1 to 1.2.2 via npm audit fix
|
I've patched the PR to address a couple of issues found during integration testing:
At the time of applying this patch, the backend was also missing I've verified that the complete flow works end-to-end: create a trip → receive 201 → navigate to the trip detail page → load the newly created trip from the backend. The real photo API and authentication integration are still pending, as originally planned. |
- Restructure README for easier onboarding and navigation - Document project status and current backend integration - Add local setup instructions using .env.example - Clarify application routes, architecture, and API data flow - Consolidate development commands and Playwright testing instructions - Update Docker and deployment configuration guidance - Summarize known limitations and link to detailed documentation
kctong529
left a comment
There was a problem hiding this comment.
The issues identified during integration testing have now been addressed, and I've verified that the trip creation and retrieval flow works end-to-end with the Go backend.
I've also added regression tests, updated the dependencies via npm audit fix, and improved the README with clearer setup instructions, .env.example, and the current backend integration status.
The remaining mock implementations and authentication integration are known limitations and can be addressed in subsequent increments.
Everything looks good for the scope of this PR.
What I added with this PR:
A landing page: When you open the site, you first see a page that explains what MapMory does. The TA asked for this at the demo gala. (I believe so)
Sign up and log in pages. "Get started" takes you to sign up, "Sign in" takes you to log in, and you can switch between them. Real login isn't connected yet, so any details open the demo account. There's also a new "Sign out" button at the top.
Every page has its own link now (like /dashboard, /map, /trips/123). So the browser's Back button works, refreshing keeps you on the same page, and you can copy a link to a trip. If you're logged out and open a trip link, it asks you to log in first and then takes you to that trip. Wrong links show a "Page not found" page.
The app can now talk to the real backend. Showing trips and creating a trip already use @kctong529's backend when VITE_API_URL is set in .env.local. Everything else still uses the fake data until the backend has those parts.
Tests for all of the above.
How to try it: