Skip to content
This repository has been archived by the owner on Jul 17, 2022. It is now read-only.

Handle 404s when dynamic paths don't point to an existing entity #102

Open
2 tasks
deammer opened this issue Mar 20, 2021 · 0 comments
Open
2 tasks

Handle 404s when dynamic paths don't point to an existing entity #102

deammer opened this issue Mar 20, 2021 · 0 comments
Labels
front end good first issue Good for newcomers help wanted Extra attention is needed
Milestone

Comments

@deammer
Copy link
Collaborator

deammer commented Mar 20, 2021

When using dynamic paths like /shipment/:shipmentId, we need to fail gracefully in case the shipmentId doesn't exist.

We should also handle invalid IDs, like "abc123" for example.

  • make inventory of all dynamic routes
  • update components that render dynamic routes and add a "entry not found" message in case the requested entries cannot be resolved.
@deammer deammer added good first issue Good for newcomers help wanted Extra attention is needed and removed help wanted Extra attention is needed labels May 15, 2021
@coderbyheart coderbyheart added this to the v2 milestone Jan 8, 2022
@coderbyheart coderbyheart added the help wanted Extra attention is needed label Jan 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
front end good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants