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
The user can change the value of compact on the client.
If the search parameters then change (in our case clicking an "Edit" button might open a modal by pushing to the same route with ?edit=true) the compact state will persist with whatever value the user has set, but the value of data will revert back to whatever the initial value was loaded from the server.
In the example above this means that if the user changed compact from true to false and then clicked an "Edit" button, the graphql data would revert back to seeing compact as true while the rest of the UI would still be seeing it as false.
Package
Version
@apollo/client
3.11.8
@apollo/experimental-nextjs-app-support
0.11.5
next
15.0.1
react
18
The text was updated successfully, but these errors were encountered:
We have a query setup that has some default variables on the server that can then change on the client. As an example:
The user can change the value of
compact
on the client.If the search parameters then change (in our case clicking an "Edit" button might open a modal by
push
ing to the same route with?edit=true
) thecompact
state will persist with whatever value the user has set, but the value ofdata
will revert back to whatever the initial value was loaded from the server.In the example above this means that if the user changed
compact
fromtrue
tofalse
and then clicked an "Edit" button, the graphql data would revert back to seeingcompact
astrue
while the rest of the UI would still be seeing it asfalse
.The text was updated successfully, but these errors were encountered: