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
Ref: #4410
For server side render: https://github.com/ReactTraining/react-router/blob/v4/packages/react-router/modules/StaticRouter.js#L115
history always be replaced by inner history. So I guess it may provide some props with each Router to make it easier for location query self handle.
in addition, how do I handle Redirect.to, Link.to && router.push when I want to use query instead of connecting the search string?
Redirect.to
Link.to
router.push
The text was updated successfully, but these errors were encountered:
You should be stringifying your query object in whatever component is rendering your <Redirect>/<Link>.
<Redirect>
<Link>
import { stringify } from 'qs' const MyComponent = () => ( <div> <Link to={{ pathname: '/some-place', search: '?' + stringify({ a: 'b', c: true }) }}>Go Here</Link> </div> )
Sorry, something went wrong.
No branches or pull requests
Ref: #4410
For server side render: https://github.com/ReactTraining/react-router/blob/v4/packages/react-router/modules/StaticRouter.js#L115
history always be replaced by inner history. So I guess it may provide some props with each Router to make it easier for location query self handle.
in addition, how do I handle
Redirect.to
,Link.to
&&router.push
when I want to use query instead of connecting the search string?The text was updated successfully, but these errors were encountered: