Similar to the letters boxed puzzles I’ve been working on, I’ve been experimenting with a small side project that retrieves structured puzzle data from a source. However, I’m encountering an odd problem when retrieving dynamic fields using apollo client.
Certain queries function flawlessly until the data structure slightly changes, such as when new puzzle nodes are added. At that point, apollo begins returning cached fragments or partial data that don’t update unless I manually reset the store.
Has anyone witnessed apollo’s difficulties with dynamic or constantly shifting node structures? I want to know if this has to do with cache normalisation, type policies, or missing id fields in specific sub-types. I’m also wondering if employing fetchPolicy: “network-only” is merely hiding the underlying problem or if it’s a good long-term solution.
I would value any insight from anyone who’s dealt with rapidly changing content structures.
