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
What is the new or updated feature that you are suggesting?
V6 removed the strict attribute from <Route> preventing the enforcement of a trailing slash in a route. I'd advocate it be reintroduced.
Why should this feature be included?
Relative links are handled differently depending on whether there is a trailing slash in the current URL. If a user is on the page example.com/foobar and there is a link with href="fizbuzz", the browser will go to example.com/fizbuzz. However if they are on the page example.com/foobar/ and they use the same link the browser will take them to example.com/foobar/fizbuzz. By removing the strict attribute it complicates taking advantage of this designed behavior in html. With the strict attribute it is possible to plan for clients to have the trailing slash and redirect direct traffic to the correct path. Without the attribute the component would need to change how links are rendered based on whether there is a trailing slash.
The text was updated successfully, but these errors were encountered:
After reading through additional documentation I see this has been given consideration. While I disagree with the decision that was made here I doubt that a random issue will change anyone's mind so I will be closing this.
What is the new or updated feature that you are suggesting?
V6 removed the
strict
attribute from<Route>
preventing the enforcement of a trailing slash in a route. I'd advocate it be reintroduced.Why should this feature be included?
Relative links are handled differently depending on whether there is a trailing slash in the current URL. If a user is on the page
example.com/foobar
and there is a link withhref="fizbuzz"
, the browser will go toexample.com/fizbuzz
. However if they are on the pageexample.com/foobar/
and they use the same link the browser will take them toexample.com/foobar/fizbuzz
. By removing thestrict
attribute it complicates taking advantage of this designed behavior in html. With thestrict
attribute it is possible to plan for clients to have the trailing slash and redirect direct traffic to the correct path. Without the attribute the component would need to change how links are rendered based on whether there is a trailing slash.The text was updated successfully, but these errors were encountered: