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
the formbuilder repository sets "DesignFields" but the graphql schema is looking for "design", so there is an error:
If you just change the schema to include "design_fields" then you get this result:
I think this is because the formRepository is using a DataObject which is nesting the field data in an array of values needing getData calls on them which GraphQl doesn't seem to be able to handle correctly.
In the FormBuilderRepository here: src/app/code/Lof/Formbuilder/Model/FormbuilderRepository.php:694
If you apply the field names directly into an array and bypass the DataObject then you get all of the values back correctly.
I was wondering if anyone else has reported this issue?
The text was updated successfully, but these errors were encountered:
When the resolver calls the form repository here:
module-formbuilder-graph-ql/Model/Resolver/Form.php
Line 70 in cf76a8f
the formbuilder repository sets "DesignFields" but the graphql schema is looking for "design", so there is an error:

If you just change the schema to include "design_fields" then you get this result:

I think this is because the formRepository is using a DataObject which is nesting the field data in an array of values needing getData calls on them which GraphQl doesn't seem to be able to handle correctly.
In the FormBuilderRepository here: src/app/code/Lof/Formbuilder/Model/FormbuilderRepository.php:694
If you apply the field names directly into an array and bypass the DataObject then you get all of the values back correctly.
I was wondering if anyone else has reported this issue?
The text was updated successfully, but these errors were encountered: