Question: Weird behaviour for Not found
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 795
- Forks
- 55
- Avg merge
- 5h 5m
- Merged PRs (30d)
- 2
Description
I have the following routeConfig.
[
{
path: '/test',
Component: () => <p>Test</p>,
},
{
path: '/test2',
Component: () => <p>Test2</p>,
},
]
I have an example here https://stackblitz.com/edit/react-ts-vzxs8c
https://react-ts-vzxs8c.stackblitz.io/test
https://react-ts-vzxs8c.stackblitz.io/ Gives me 404, but it is matching / App right then why it is giving a not found page? We should pass not found to the App instead?
If I want to configure it in this way what should I do?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the behavior using the linked StackBlitz example and inspect how the shown routeConfig handles / versus unmatched paths. Determine whether the observed 404 is expected or a routing defect; done means the behavior and the configuration needed for the requested setup are clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100