You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 10, 2021. It is now read-only.
Describe the bug
The BrowserRouter is imported and used in index.js but no Routes are being used to render specific Components in App.js , which leads to same render for all the routes. Also, because of this, the component not-found never renders for unknown urls.
To Reproduce
Steps to reproduce the behavior:
Go to 'localhost:3000/'
This should render the home-page component.
But because of no Routes being used, going to 'localhost:3000/any-string' still renders the home-page and does not render not-found component.
Expected behavior
Going to localhost:3000/ should render home-page component and for all other unknown routes like 'localhost:3000/example' should render not-found component.
Screenshots
See the URL.
Desktop (please complete the following information):
OS: [Windows 10 home, any]
Browser [Chrome, any]
Version [89.0.4389.114, any]
Smartphone (please complete the following information):
Describe the bug
The
BrowserRouteris imported and used inindex.jsbut noRoutesare being used to render specific Components inApp.js, which leads to same render for all the routes. Also, because of this, the componentnot-foundnever renders for unknown urls.To Reproduce
Steps to reproduce the behavior:
home-pagecomponent.Routesbeing used, going to 'localhost:3000/any-string' still renders thehome-pageand does not rendernot-foundcomponent.Expected behavior
Going to
localhost:3000/should renderhome-pagecomponent and for all other unknown routes like 'localhost:3000/example' should rendernot-foundcomponent.Screenshots

See the URL.
Desktop (please complete the following information):
Smartphone (please complete the following information):