-
Notifications
You must be signed in to change notification settings - Fork 185
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
The ability to use dyanmicFields in children fields. #479
Comments
ah, that's a bug! I can fix it. You'll still want to make sure the fields returned by Thanks for reporting! |
This issue has been copied into our private issue tracker (as PDE-3003). Thanks for the report! We'll update this as we learn more. |
The same function I'm using on the child field is being used on another action as a primary inputField and it's working fine. |
You can reuse the function, you just want to avoid this: fields: [
{ key: 'name' },
children: [
() => { key: 'name' }
]
] Though, now that I look, I think I've fixed this issue before. What version of |
Ah ok, I realized what's going on. The actual issue is that the The functional validator that checks for unique keys is throwing an error because it doesn't expect non-objects in So, there's two things here:
For 1 - we can file the request with our editor team. They'll know best whether that's possible or not. For 2 - consider not using |
@xavdid Thank you for the recommendation. This particular action has lots of fields so being able to group a subset with children was going to be a nice enhancement, but maybe another day! Thank you for your help! |
@xavdid Is there another way to group fields? I can't recall seeing anything in the documentation. |
There's not another way to group fields at this time, but it's a common request. It's definitely on our radar! A lot of people reach for |
Okay, thanks for letting me know. I look forward to what you all come up with. In this particular case, the UI and the data structure of children is ideal, so I hope that children can support dynamicFields at some point! Thanks again for all your help! |
Current Behavior
I received this error: inputField keys must be unique for each action, even if they're children. The key "undefined" is already in use at creates.x.operation.inputFields[5].children[2].key
Desired Behavior
The text was updated successfully, but these errors were encountered: