Skip to content
New issue

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

[Bug]: #8468

Closed
c0d3x opened this issue Dec 10, 2021 · 1 comment
Closed

[Bug]: #8468

c0d3x opened this issue Dec 10, 2021 · 1 comment
Labels

Comments

@c0d3x
Copy link

c0d3x commented Dec 10, 2021

What version of React Router are you using?

6

Steps to Reproduce

import { createHashHistory } from 'history';

const customHistory = createHashHistory();

customHistory.push('/my-route')

Expected Behavior

The route should be re-rendered.

Actual Behavior

When using a hashRouter and triggering a new location change after a back-end request returns within an action.ts file.
The route will change in the URL, but the component is not rendered.

If there is a new way of doing this, please update the manual how you can trigger the navigation not having to rely on react hooks.

This problem is mainly for external actions files and class components.

@c0d3x c0d3x added the bug label Dec 10, 2021
@timdorr
Copy link
Member

timdorr commented Dec 10, 2021

Duplicate of #8264

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants