You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my app, I have a series of QueryRenderers (some nested inside each other) that are pulling data. When I disable javascript in my browser, I expect it to render the full page properly on the server, and give it to me, however, this does not happen.
Posted here, since I think this is a problem centric to the server-side render, and not specifically relay.
I have searched the issues of this repository and believe that this is not a duplicate.
Expected Behavior
Server side should render the full app, after all the QueryRenderer calls complete.
Current Behavior
It appears that after the fetch, the QueryRenderer#render prop is not called again on the server.
Steps to Reproduce (for bugs)
Add relay and a working query renderer to your app
Have the result just output the result as text
Disable javascript in your browser
Reload the page, you won't see the result text.
Context
Your Environment
Tech
Version
next
5.0.0
node
8.9.4
OS
osx sierra 10.12.6
browser
Chrome Version 66.0.3359.117 (Official Build) (64-bit)
The text was updated successfully, but these errors were encountered:
[This example] demonstrates the intended pattern for next.js with Relay-Modern. Indeed you want to run your query in getInitialProps as you can see in there 👍
In my app, I have a series of QueryRenderers (some nested inside each other) that are pulling data. When I disable javascript in my browser, I expect it to render the full page properly on the server, and give it to me, however, this does not happen.
Posted here, since I think this is a problem centric to the server-side render, and not specifically relay.
Expected Behavior
Server side should render the full app, after all the QueryRenderer calls complete.
Current Behavior
It appears that after the fetch, the
QueryRenderer#render
prop is not called again on the server.Steps to Reproduce (for bugs)
Context
Your Environment
The text was updated successfully, but these errors were encountered: