menu
Channels
Team
Posts
Members
Info

Generating typescript typed local resolvers?

Anyone found a way to generate typescript typings for local state resolvers? Because my local state schema involves a lot of "extend type"s and can't be codegen'd on it's own. Thanks!

thumbsup
1
message-simple
3

Default local state

Hi, I'm using react-apollo, and in the apollo's web site shows the 'defaults' property is deprecated that we have to writeData directly to the cache. I'm saving a boolean to know if the user enable or disable something, I do the writeData to true, open the app and it is true but鈥

thumbsup
0
message-simple
0

Same data entity in two locations in the cache

I have a use-case for holding the same data entity (same id) in two locations in the cache, is there documentation surrounding this? Is this supported? Thanks

thumbsup
0
message-simple
0

Local state and Apollo Client Developer Tools

I have a simple app that uses a GraphQL API and local state: https://codesandbox.io/s/github/454de6e/ip-country-lookup The local state is just one field ip. 鈥

thumbsup
1
message-simple
4

Array in State

Why if I add to the default String then everything works, and if I put the array, then after the renderer in the array is empty? https://gist.github.com/gHashTag/b4cab5b3e5db4792a4e27fc28ea7065b.js

thumbsup
0
message-simple
0

Apollo (with vue) local state mutations silently fail?

Hey - I've been hitting a lot of trouble working with local state mutations in vue, because I the way the system is set up, is seems to silently fail. Is there a way to make failures noisier? I have resolvers set up roughly like so Given this, calling a mutate with a typo will鈥

thumbsup
0
message-simple
0

Local mutation resolver not working

This is my client but when I call the mutation The resolver function never gets called. Any help would be appreciated```

thumbsup
1
message-simple
8
Alex31d

Is writeQuery not necessary in local resolvers?

I discovered that following code works exactly like this one Can some one show me any words about that in doc?

thumbsup
0
message-simple
0

Heuristic fragment matcher warning

While writing the cache in a client-side resolver, I get this warning which is unnecessary since I'm not using unions or interfaces. Here is the code in the client app that throws the warning: I don't even think using fragmentMatcher on the cache will solve this since it's a鈥

thumbsup
0
message-simple
2
K.35d

Subscriptions in local state

I've looked at whether it is possible to define/publish subscriptions on the client side with local state management, but unfortunately come to the conclusion that this is currently not possible. There's an issue asking the same thing, but there hasn't been an answer:鈥

thumbsup
0
message-simple
2