-
Notifications
You must be signed in to change notification settings - Fork 20
Value of Deep #8
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
Comments
Hello, I thnink, there is a bug in the readOnly function. Can you provide a full example of your problem ? Thanks ! |
Hello, I can confirm that there is a problem on deep calculation... As said previously, readOnly has the trouble. Thanks ! |
Yes, I've noticed the problem when trying to print deep inside the function passed to readOnly. My example is pretty similar to the one I've given above, except that y is an empty array instead of an empty object. |
Hello, Ok. I just wanted to know if the readOnly function was the only one that have this bug :). |
I've just published the 2.2.1 with the fix. Can you tell me if it is correct now ? It should be, but I prefer your confirmation :). |
Yes, the error seems to be fixed! |
Cool :). Happy to see that ! |
Hi, I have a question about how we define the deep value of a node. Considering the example
data={x: "a string value", y: {z: "y is an object"}};
I expected x and y to have the same deep. But y, being an object, gets the value deep + 1. Is this a bug, if not could you please help me understand why you chose this design.The text was updated successfully, but these errors were encountered: