Open djeeg opened 8 years ago
I'm facing at this problem too. Turning SSR off was my temporary fix.
Having the same issue, turned off SSR and it worked for me, thanks @hanjukim
What is SSR? and how to turn it off?
@FrankPaul1 - it's Server Side Rendering
Hey @sars, this async project works really well, easy to understand and integrate, especially the new deferred vs not-deferred logic Thought I'd report this slight issue First point to note, this is not an issue when using client-side navigation It only becomes a problem on the initial server-side page request
I have a page, where I want the server to render 20% (fast) of an object and leave the client to fetch the other 80% (slow) 20% of the object is enough to push out the SEO tags
asyncConnect is setup like this:
And the server bindings: (a bit messy as using TS with no spread, and https://github.com/Rezonans/redux-async-connect/issues/55#issuecomment-204619076)
And client bindings:
The problem I have, is that I would expect that on server render, the server waits for fetchShallowUserThunk (which it does) And then the client should trigger fetchDeepUserThunk (which it doesn't) It is like the [deferred: true] flag does not do anything
I can work around this by doing something like this
Though, that's not ideal as I multiple calls to fetchDeepUserThunk
Have I missed something? Cheers