-
-
Notifications
You must be signed in to change notification settings - Fork 265
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
fix getInitialPageProps return #378
Conversation
I think this part is forgotten.
What issue are you trying to solve? |
Hi, When i return
In getInitialProps, I expect to get |
This is exactly how it works. You will get your props unwrapped. The internal objects are needed for transport, you should never see them in your own components. If you do - that’s a bug, and it should be fixed. Can you create a sandbox to illustrate it if you see the internals. |
fixed |
I see now, thank you. Let me check why they are leaking. |
This has to be fixed slightly differently, I'm closing this PR, I've referenced the PR in the correct fix fc056a9. Thank you for contributing. |
At least in my environment I got props inside props still after your fix.
|
It was because just I forget to run npm build on parent dir. Sorry >_< |
Just we should wait for saga in getInitialPageProps(). |
I think this part is forgotten.