-
Notifications
You must be signed in to change notification settings - Fork 104
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
Component doesn't rerender on props change #90
Comments
This happens because current version can't "wait" for requests to finish. It supposed to be fixed in API v2 #30 |
I suppose the same happens with the google crawler bot. |
@stereobooster do you have any information on when it will be merged? |
It is not finished. No information on when it will be merged |
API v2 alone can be not sufficient for your case. Assume pre-renderer waited long enough, to render all HTML. On the client side browser receives all HTML, React application starts to execute, its state is empty, React erases prerendered HTML and places "Loading" starts to do AJAX request to get data. What you can do is:
If you would use async components, you would need to store a state of loaded components too. For example like in loadable-components |
Hi. Sorry if it is a duplicate but here is the issue:
AppRoot
Component:here is the console from the browser:
(I have a bunch of other debugging
console.warn
in other parts as you can see. They are just displaying the request was successful so that the Redux store would update as expected.)But when I run the react-snapshot, here is what I'm getting:
As you see, the render is called only once, and the
componentWillReceiveProps
has not been called at all.So it always renders the following as the snapshot:
The text was updated successfully, but these errors were encountered: