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
Description
I have nested objects with a few dependencies in those objects. Whenever an inner object has dependencies making a field rquired based on another one having a value and if the object is required by the parent it throws an error
In the example if you remove the required array on line 67 the error goes away or if you remove the dependencies in line 62 it works. It's something about that combination that is making it break.
When it's broken you can see that the radio button doesn't actually change the fields that correspond to the value in the oneOf, when it works you can see the fields change when you change the option.
Your Environment
Angular version: 10.2.5
Formly version: 5.10.21
Additional context
We don't have these problems when running version 5.10.18, when we tried to upgrade to 5.10.21 our application became unusable because of this.
I did some testing and this issue starts showing on version 5.10.19
The text was updated successfully, but these errors were encountered:
Description
I have nested objects with a few dependencies in those objects. Whenever an inner object has dependencies making a field rquired based on another one having a value and if the object is required by the parent it throws an error
Error: [Formly Error] [Expression "templateOptions.required"] Cannot read property 'middleName' of undefined
It's going to be easier to see it than to explain it with words.
Minimal Reproduction
https://stackblitz.com/edit/issue-with-v21?file=src%2Fapp%2Fapp.component.ts
In the example if you remove the required array on line 67 the error goes away or if you remove the dependencies in line 62 it works. It's something about that combination that is making it break.
When it's broken you can see that the radio button doesn't actually change the fields that correspond to the value in the oneOf, when it works you can see the fields change when you change the option.
Your Environment
Additional context
We don't have these problems when running version 5.10.18, when we tried to upgrade to 5.10.21 our application became unusable because of this.
I did some testing and this issue starts showing on version 5.10.19
The text was updated successfully, but these errors were encountered: