handling null from store.delete about relay-compiler-language-typescript HOT 5 CLOSED

I think your updater function has to delete the entry in the list as well - or your mutation payload should include some way to re-query the list field such that you can update the store in the proper way when you call your mutation. Can you provide a more complete example (a repository with a repro would be good)? Then I'll happily try to assist you?

from relay-compiler-language-typescript.

oh nice, that's how i do it today-- the mutation payload includes the primary key removed & a foreign key which I can match with the name of every connection & list it can possibly belong to.

The tension is that the usage of a public API method (store.delete) can render a static type invalid, which kinda defeats the purpose of types. is there something we can do, or should it just be a rule to never use this method?

from relay-compiler-language-typescript.

Well first I'd test whether this is true when using Relay with flow (which I'm almost certain it is) - if that's the case then this issue should be posted in the Relay repo itself. We don't really control how the APIs work, we've only tried to replicate what is happening for Flow and port it to TypeScript.

from relay-compiler-language-typescript.

agreed! i'm just afraid it'll fall into a into the relay backlog black hole.
i'm mostly looking for a best practice here-- do you avoid calls to store.delete or is it just assumed that your team always cleans up after a delete?

from relay-compiler-language-typescript.

the relay backlog black hole

😞

As for the best practice, I can’t really offer any advice offhand, as our front-end apps only do the CRU part of CRUD atm, so would also have to play with an example app.

from relay-compiler-language-typescript.