Is there a reason MutationObserver.#updateResult is private?
Hey! I made a MobX adapter for TanStack Query v4. It works great - we have a
MobxQuery, MobxMutation and MobxQueries that are same as the corresponding React hooks, reactivity works, everything is well.
When trying to upgrade to v5, MobxMutation no longer works. The reason is, at some point in the lifecycle, I called the "private" function updateResult on my local MutationObserver instance. In v4 it was just a Typescript "private" so calling it worked on runtime. Not optimal but fits my needs.
Now in v5 it's actually nonexistent outside of the class. My adapter behavior relies on calling this.
I can go into more details about the adapter implementation, and maybe you'll have a better idea for how to do things - but my first question is, is there a reason updateResult is private? For comparison, it's public on QueryObserver. Thanks! 🫶🏻0 Replies