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
As a developer I want exact route matching to be the default so that the routing config is more intuitive and wrong URLs are easier to detect.
DoD:
Vaadin.Resolver is updated so that if a route does not have an exact property it matches a route only if the given pathname exactly matches the route path (trailing slashes are optional).
the specs for resolveRoute and Vaadin.Resolver are updated
The text was updated successfully, but these errors were encountered:
- re-arrange the test cases in the matchRoute() spec to clarify "" and "/" routes matching and the role of the trailing and leading "/" in the route paths
- update the matchRoute() implementation to match the updated spec
- remove the `exact` property from the Vaadin.Router JSDocs and specs
Fixes#64
As a developer I want exact route matching to be the default so that the routing config is more intuitive and wrong URLs are easier to detect.
DoD:
exact
property it matches a route only if the given pathname exactly matches the route path (trailing slashes are optional).resolveRoute
andVaadin.Resolver
are updatedThe text was updated successfully, but these errors were encountered: