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
since @apollo/client@3.0.0-beta.44 all the @client directives on fields throw a MissingFieldError when trying to render on the server (using @apollo/react-ssr@4.0.0-beta.1)
When downgrading to @apollo/client@3.0.0-beta.41 it works as usual.
Does @apollo/client@3.0.0-beta.44 introduced a breaking change on the way it handles @client directives ?
The text was updated successfully, but these errors were encountered:
We did remove the option to pass @client directives into the link chain, which is documented in the link section of the Migration Guide. It isn't clear though if that is the issue being originally reported here? @nathanschwarz if this isn't your problem, could you provide more details, such as a small runnable reproduction? Closing for now, but happy to re-open if this issue isn't resolved.
It seems that the bug was removed with @apollo/client@3.0.0-beta.50.
Anyway, I wasn't using the old apollo-link-state API, but the one in the core (just to clarify, I can guess that apollo-link-state is still implemented in the core). It seems that @client directives were sent to server anyway even with local resolvers setup.
Hello there,
since
@apollo/client@3.0.0-beta.44
all the@client
directives on fields throw aMissingFieldError
when trying to render on the server (using@apollo/react-ssr@4.0.0-beta.1
)When downgrading to
@apollo/client@3.0.0-beta.41
it works as usual.Does
@apollo/client@3.0.0-beta.44
introduced a breaking change on the way it handles@client
directives ?The text was updated successfully, but these errors were encountered: