-
Notifications
You must be signed in to change notification settings - Fork 217
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
Unhandled JS Exception when one of the item in object is a React-Native element #76
Comments
I'm guessing that the React/React Native objects have cycles somewhere in their properties. I assume that you are expecting the React Native objects to not be merged? Can you find out if there's a canonical way to detect the React Native object type? If so, we can add it to is-mergeable-object, which would fix the issue in your case. |
@TehShrike I'm not expecting to merge the React Native objects but to get the last one indeed. Both objects are quite similar: One has a defined Although I would think the same rule should apply and we shouldn't merge ReactJS element either. We can create a check for |
Check over TehShrike/is-mergeable-object#1 |
Any thoughts @alexmngn? |
It would be interesting to support merging circular references since in theory it would be possible. |
@TehShrike Looks good to me 👍 |
Which prevents attempting to merge React elements, fixing #76
Published as 1.5.2. |
I have 2 objects I'd like to deep merge. One element in the object is a React-Native element.
First object:
I get the following error when I try to merge those 2 objects:
The text was updated successfully, but these errors were encountered: