feat: legacy router migration 4#131
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
*Lighthouse ran on https://mobilitydatabase-hb5qydjvn-mobility-data.vercel.app/ * (Desktop)
*Lighthouse ran on https://mobilitydatabase-hb5qydjvn-mobility-data.vercel.app/feeds * (Desktop)
*Lighthouse ran on https://mobilitydatabase-hb5qydjvn-mobility-data.vercel.app/feeds/gtfs/mdb-2126 * (Desktop)
*Lighthouse ran on https://mobilitydatabase-hb5qydjvn-mobility-data.vercel.app/feeds/gtfs_rt/mdb-2585 * (Desktop)
*Lighthouse ran on https://mobilitydatabase-hb5qydjvn-mobility-data.vercel.app/feeds/gbfs/gbfs-flamingo_porirua * (Desktop)
|
|
|
||
| // TODO: Once the [...slug] catch-all route is removed, replace this wrapper | ||
| // with a (protected) route group layout that provides auth guarding at the layout level. | ||
| // TODO: Replace this wrapper with a (protected) route group layout that |
There was a problem hiding this comment.
Do we have an issue for following up on this?
Summary:
closes #26
Removes the legacy router and all traces of the old React App
Expected behavior:
App should run as usual
Testing tips:
Provide tips, procedures and sample files on how to test the feature.
Testers are invited to follow the tips AND to try anything they deem relevant outside the bounds of the testing tips.
Please make sure these boxes are checked before submitting your pull request - thanks!
yarn testto make sure you didn't break anything