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 Mar 23, 2023. It is now read-only.
These are internal and implementation details of how React builds for npm. We're going to deprecate them. merge is now simply Object.assign and copyProperties is a simple for in (and can be replaced with Object.assign)
The text was updated successfully, but these errors were encountered:
What's your position on this now, with the release of 0.12 with deprecation warnings for merge/copyProperties and the provision of Object.assign in react/lib? Is it okay for the examples to simply be updated to use react/lib/Object.assign instead, or will even that be very quickly moved out of React entirely?
My understanding is that FB is working on exposing Object.assign in a way that can be shared across projects, not just within React. But we're not there yet. So I am thinking about using Sindre's npm module for Object.assign until then.
These are internal and implementation details of how React builds for npm. We're going to deprecate them.
merge
is now simplyObject.assign
andcopyProperties
is a simplefor in
(and can be replaced withObject.assign
)The text was updated successfully, but these errors were encountered: