Query components rerender when unrelated subscriptions fire

[robinmbarnes]

Intended outcome:

When subscriptions update, only they rerender, not other query components with unrelated queries.

Actual outcome:
When subscriptions update, other unrelated query components (not nested within the subscriptions) rerender.

How to reproduce the issue:

Add both a and a to an app, querying data not related to one another. When the subscription fires, the query also rerenders.

Version

• [email protected]
• [email protected]

[rosskevin]

Wonder if related to #2398 (comment)

[rosskevin]

I'm going to insist on a reproduction here. We have open issues on rerendering and there are plenty of opportunities for a subscription result to pact the cache of another query depending on the user setup and schema.

We are going to work on some codesandboxes to try and help with reproductions, but as-is based on the information stated, it could be desired behavior or user misunderstanding of the observable and structure of the cache.

[isaiahtaylorhh]

Getting the same issue. My situation is that I have a component which is associated with a schema objects, and then child components which are related to sub-fields of that schema object, which are connections to other tables. I have a poll interval on one of these subfields, but it causes the parents to re-render. Any way to only have the specific component and its children re-render?