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
Since the upgrade to 2.3.0rc1, unnested properties cause an error on validate when the parent property is nil, which was not the case in 2.2.0. Is this intended? Is there any workaround?
This form is used as the item form for a collection property in another form, which has a populator that finds or creates a vendor_fulfillment for the incoming fulfillment_service_id, using nil if it can't find one or fulfillment_service_id is nil, and then uses it in a VendorLineItem.
Now, I don't actually want vendor_fulfillment to be nil, and I have validation that verifies that it is not and that the fulfillment_service_id belongs to a scoped set of ids.
This worked in 2.2.0, but after upgrading to 2.3.0rc1 it raises after population has run but before it gets to my validation:
Since the upgrade to 2.3.0rc1, unnested properties cause an error on validate when the parent property is nil, which was not the case in 2.2.0. Is this intended? Is there any workaround?
Steps to reproduce
This form is used as the item form for a collection property in another form, which has a populator that finds or creates a vendor_fulfillment for the incoming fulfillment_service_id, using nil if it can't find one or fulfillment_service_id is nil, and then uses it in a VendorLineItem.
Now, I don't actually want vendor_fulfillment to be nil, and I have validation that verifies that it is not and that the fulfillment_service_id belongs to a scoped set of ids.
This worked in 2.2.0, but after upgrading to 2.3.0rc1 it raises after population has run but before it gets to my validation:
is there a workaround, or do I always have to create an empty VendorFulfillment in my populator if I want to use unnest on its properties?
The text was updated successfully, but these errors were encountered: