-
Notifications
You must be signed in to change notification settings - Fork 961
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
Add forceRefresh option to createBrowserHistory #95
Comments
The other option would be to just make this an option on |
Oh, so if the browser doesn't support I'm open to figuring out a way to do this in userland, if the demand for it isn't enough to warrant the feature (I know how much a feature costs, maintenance/docs/etc). |
@taion you beat me by a few seconds :p |
Good point, @taion. Let's try that first: adding an |
That would solve everything! |
BTW, because every issue is actually the same issue, this ties into remix-run/react-router#2211. Adding something like |
@taion It depends on how you view react-router; I viewed it as a project that literally wrapped But no need to go into it here :) I'm fine with the decision in there. |
Maybe call it |
It's not a method, @timdorr. It's an option to the create step. let history = createBrowserHistory({ forceRefresh: true }) |
Whooooops! Nevermind me 😄 |
add support for forceRefresh addresses issue: remix-run#95
addresses issue: remix-run#95
Resolved in #100 |
Some users need a history that:
pushState
See also remix-run/react-router#2243
The text was updated successfully, but these errors were encountered: