I fixed it in the article: we use writeData, not writeQuery ;)
I rather meant in the mutations inside the resolver. With client.writeQuery you can make sure, the data reactivity is triggered for sure while cache.writeQuery will possible not fire a data refresh in your UI if you change nested items. At least that's what I currently can reproduce.
I cannot reproduce this behavior and very own Apollo tutorials are also relying on cache.writeData and cache.writeQuery
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.