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
<Route exact path="/path/:id/:additional?" component={userIsAuth(MyComponent)} />
Will always fire Component lifecycle as componentWillMount() for location changes and rerender it again and again.
If I use just MyComponent without userIsAuth wrapper it works good without any remounting.
<Route exact path="/cottages/:id/:optional?" component={MyComponent} />
const userIsAuth = connectedRouterRedirect({ redirectPath: '/login', authenticatedSelector: ({ user }) => authenticatedSelector(user), wrapperDisplayName: 'UserIsAuthenticated', authenticatingSelector: ({ user }) => authenticatingSelector(user), AuthenticatingComponent: LoadingScreen, redirectQueryParamName: 'next', });
Is it bug or any possibility to fix this behaviour?
The text was updated successfully, but these errors were encountered:
I think this is the same as #224. Take a look at https://mjrussell.github.io/redux-auth-wrapper/docs/Getting-Started/Overview.html#where-to-apply. You may need to apply the HOC (i.e. userIsAuth(MyComponent)) outside the Route and pass it in
userIsAuth(MyComponent)
Route
Sorry, something went wrong.
@mjrussell thank you. Yes, it's the same issue like #224
For now workaround from @dtweedle fixed the problem #224 (comment)
const myComponentWrapped = userIsAuth(MyComponent); <Route exact path="/path/:id/:additional?" component={myComponentWrapped} />
Will watch another issue.
No branches or pull requests
Will always fire Component lifecycle as componentWillMount() for location changes and rerender it again and again.
If I use just MyComponent without userIsAuth wrapper it works good without any remounting.
Is it bug or any possibility to fix this behaviour?
The text was updated successfully, but these errors were encountered: