We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maybe a breaking change but I think we need this.
From Readme:
<Router> <Route exact>Hello World</Route> <Route exact path="/svelte-component" component={SvelteComponent}/> <Route exact path="/promise" component={import('path/to/other-component.svelte')}/> <Route exact path="/async" component={() => import('path/to/another-component.svelte')}/> </Router>
Can we omit exact? Can we use it as default?
exact
All my routes are exact.
Can we use not-exact or similar for when not exact?
not-exact
The text was updated successfully, but these errors were encountered:
Nope, I mean, we could add exact support on top-level <Router /> so it just inherit down.
<Router />
But making it default will break nested routes and such.
What do you think?
Sorry, something went wrong.
feat: enable top-level exact default, close #29
98ab996
100d658
No branches or pull requests
Maybe a breaking change but I think we need this.
From Readme:
Can we omit
exact
? Can we use it as default?All my routes are
exact
.Can we use
not-exact
or similar for when not exact?The text was updated successfully, but these errors were encountered: