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

Play nicely with react-hot-loader #126

Closed
wants to merge 1 commit into from

Conversation

pugnascotia
Copy link

react-hot-loader's component proxying was breaking direct comparisons with the Redirect component type. Fix this using a suggested approach from gaearon/react-hot-loader#304.

@JannesV
Copy link

JannesV commented Oct 2, 2018

Is this getting merged anytime soon ?

react-hot-loader's component proxying was breaking direct comparisons
with the `Redirect` component type. Fix this using a suggested approach
from gaearon/react-hot-loader#304.
@pugnascotia
Copy link
Author

Rebased on latest master.

@peter-mouland
Copy link

I'm not part of this project, but you might have a better chance of it being merged if there were some tests?

@rlueder
Copy link

rlueder commented Jan 24, 2019

For those landing here with the same issue related to react-hot-loader breaking, an easy workaround is described here: #153 (comment)

TLDR; use "path" instead of "from" in the Redirect component: <Redirect path="/" to="yourpath" />

@joelgallant
Copy link
Contributor

More conservatively, this could do the "static member" strategy, if there's any fear of breakage here.

Just ran in to a production bug with this, where the warning/error did not show up in development.

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

Successfully merging this pull request may close these issues.

5 participants