Closed benfeather closed 1 month ago
This is probably the only instance of a field being a condition sub-field. But looks like useMultipleFields
is missing from the Name field interface. I think having that available is what we'll go for, compared to other options for simplicity.
Fixed for the next release. To get this early, run composer require verbb/formie:"dev-craft-5 as 3.0.0-beta.9"
.
Sounds good to me, Thanks!
Describe the bug
I'm using Formie with the GraphQL API, but there's no field to determine whether a form control should use the nested fields. For example, here is the GQL fragment for the Name control:
Which returns this JSON, as expected:
However, if I disable the "Use multiple name fields" option, the response still returns the nested fields.
Ideally, when disabling the "Use multiple name fields" option, either:
Then, on the front end, we can either check if the prop is enabled or if the nestedRows prop is empty and render the correct field layout.
I may be missing something, but I couldn't see this property in GraphiQL.
Steps to reproduce
N/A
Form settings
Craft CMS version
5.1.0
Plugin version
dev-craft-5 as 3.0.0-beta.4
Multi-site?
Yes
Additional context
Using the dev-craft-5 version as it fixes the Stripe dep issue.