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
In previous version of history package the basename was also used for making location.pathname relative to basename, see history v4 api
history
basename
location.pathname
history v4 api
For example with basename /foo/bar/id and url /foo/bar/id/baz the pathname will be /baz
/foo/bar/id
/foo/bar/id/baz
pathname
/baz
Then in the 5th version they removed basename support silently.
I am seeing that you've added support for basename in v5.1.0
So I am wondering are there any plans to expose relative pathname under router.location in redux store?
router.location
The text was updated successfully, but these errors were encountered:
Any updates on this issue?
Sorry, something went wrong.
No branches or pull requests
In previous version of
history
package thebasename
was also used for makinglocation.pathname
relative tobasename
, seehistory v4 api
For example with
basename
/foo/bar/id
and url/foo/bar/id/baz
thepathname
will be/baz
Then in the 5th version they removed basename support silently.
I am seeing that you've added support for
basename
in v5.1.0So I am wondering are there any plans to expose relative
pathname
underrouter.location
in redux store?The text was updated successfully, but these errors were encountered: