GraphQL.prototype.forceRenderChildren should use forceUpdate() and not setState({}) #773
Comments
This issue has been automatically marked as stale becuase it has not had recent activity. It will be closed if not further activity occurs. Thank you for your contributions to React Apollo! |
This issue has been automatically labled because it has not had recent activity. If you have not received a response from anyone, please mention the repository maintainer (most likely @jbaxleyiii). It will be closed if no further activity occurs. Thank you for your contributions to React Apollo! |
This issue has been automatically labled because it has not had recent activity. If you have not received a response from anyone, please mention the repository maintainer (most likely @jbaxleyiii). It will be closed if no further activity occurs. Thank you for your contributions to React Apollo! |
This issue has been automatically closed because it has not had recent activity after being marked as no recent activyt. If you belive this issue is still a problem or should be reopened, please reopen it! Thank you for your contributions to React Apollo! |
Buggy Behavior
GraphQL.prototype.forceRenderChildren is using setState to force a re-render, which breaks shallow equals rendering optimizations.
Expected Behavior
Use the React API forceUpdate() instead.
Version
The text was updated successfully, but these errors were encountered: