Ian MacLeod

I think really what you want here is for Hermes to support [unvalidated writes (e.g. `writeData`)](https://github.com/convoyinc/apollo-cache-hermes/issues/333)

Another potential option could be for hermes to _assert_ that `__typename` is present in all nodes when `addTypename` is true

FWIW, I'm pretty sure inmemory cache has the same behavior here

So the error here is that you originally selected a field as a non-entity (e.g. without an `id` field), but in a subsequent request, selected it as an entity (with...

TL;DR - make sure all fragments for that entity select the `id` field (or that none of them do; but I'm pretty sure that's not what you want in this...

Let's leave this issue open as a reminder that that error could use some more documentation

Hmm, @boorad, the cache generally doesn't care how you reach a given entity (via query, fragment, etc); for this error, I think what is likely is that you've queried an...

…also, wow, I really need to address #66 :(

And for the `writeFragment` call, you're doing something like: ```ts cache.writeFragment({ id: 'someroundid', fragment: scoreFragment, data: {…} }); ``` ?

Welp, I think I'm going to call this one a bug! Thanks for the details here, I've got a reproduction case that hits this 👍 The cache is getting confused...