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
Is your feature request related to a problem? Please describe.
People choose Gravity Forms for its extensibility. While v0.10 made much progress to help devs support custom form fields, it still requires several filters to make work.
We should explore ways to make this even easier in WPGraphQL for GF, ideally by offering a single function that handles all the heavy lifting.
Describe the solution you'd like
In theory, a register_graphql_gf_form_field() function that resembles its namesake.
The function should let users
Define the necessary GraphQL fields on the autogenerated FormField object.
Define the FormFieldValueInput field for mutation support.
Let you overwrite the autogenerated FormField object type name.
Function arguments and usage should be as similar to core WPGraphQL register_graphql_{} functions as possible.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
People choose Gravity Forms for its extensibility. While v0.10 made much progress to help devs support custom form fields, it still requires several filters to make work.
We should explore ways to make this even easier in WPGraphQL for GF, ideally by offering a single function that handles all the heavy lifting.
Describe the solution you'd like
In theory, a
register_graphql_gf_form_field()
function that resembles its namesake.The function should let users
Function arguments and usage should be as similar to core WPGraphQL
register_graphql_{}
functions as possible.The text was updated successfully, but these errors were encountered: