You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.
Intended outcome:
when using graphql(query)(Component), I'd expect the injected data prop to be immutable so React components extending React.PureComponent would pick up the change and only re-render as necessary
Actual outcome: props.data is not always immutably regenerated, and therefore will fail the PureComponent strict equality test for determining is a rerender is necessary
How to reproduce the issue:
Create a component extending PureComponent, and using the graphql() HOC with an uncached query. The child component should not update when the query resolves and the network status changes for the second time.
Intended outcome:
when using
graphql(query)(Component)
, I'd expect the injecteddata
prop to be immutable so React components extendingReact.PureComponent
would pick up the change and only re-render as necessaryActual outcome:
props.data
is not always immutably regenerated, and therefore will fail thePureComponent
strict equality test for determining is a rerender is necessaryHow to reproduce the issue:
Create a component extending PureComponent, and using the graphql() HOC with an uncached query. The child component should not update when the query resolves and the network status changes for the second time.
Version
The text was updated successfully, but these errors were encountered: