-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix mutating array datasource bug #1109
Fix mutating array datasource bug #1109
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice. Thanks @KashishGoel ! 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh actually, please add a changelog entry for this for 3.3.0
😊
@KashishGoel responding to the Test question here. Actually think a Test would be awesome for the longevity of this fix! Would be really easy:
You can init a new SC without setting up the rest of the IGLK infra even. Sent with GitHawk |
@KashishGoel has updated the pull request. View: changes |
@KashishGoel has updated the pull request. View: changes |
@rnystrom Added a test, should be enough to ensure we don't run into this problem again. |
@KashishGoel its perfect 😇 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rnystrom is landing this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
Changes in this pull request
Copy objects when retrieving from datasource to account for the edge case where the returned data is a mutable array.
Issue fixed: #999
Checklist
CHANGELOG.md
for any breaking changes, enhancements, or bug fixes.