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
Only the first element of the nested class added to the object is added with the _id field. Every object that I add more has the _id field absent, or removed if passed along in new NestedClass({ _id: 'something' });.
I've tried playing with setting different combinations of optional, default and immutable and it always boils down to immutable. When that's set to false - it works fine.
Turning it off is fine as a temporary solution, but if this issue can't be fixed I'll have to think of some additional verification to make sure that my ID stays untouched.
Is that a bug? Can that be fixed?
Thank you for this great package!
The text was updated successfully, but these errors were encountered:
I can confirm this bug. If a nested field is set to immutable then only the first nested element will contain those values. Subsequently added nested element will not containe the immutable values. My code is as follows:
I'm using a nested class with an _id field that I'd like to have be unique and readOnly. This is my setup:
Only the first element of the nested class added to the object is added with the _id field. Every object that I add more has the _id field absent, or removed if passed along in
new NestedClass({ _id: 'something' });
.I've tried playing with setting different combinations of
optional
,default
andimmutable
and it always boils down toimmutable
. When that's set to false - it works fine.Turning it off is fine as a temporary solution, but if this issue can't be fixed I'll have to think of some additional verification to make sure that my ID stays untouched.
Is that a bug? Can that be fixed?
Thank you for this great package!
The text was updated successfully, but these errors were encountered: