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
{{ message }}
This repository has been archived by the owner on Jul 23, 2024. It is now read-only.
I am using graphql to expose certain post types with some associate data to some javascript calendar component.
If I am modifying an unrelated fieldset, a layout field for example, "show in graphql " defaults to active and subsequently requires to fill "graphql field name", this has become an annoyance.
This default behavior would rather be opt-in, that you could select on general settings.
The text was updated successfully, but these errors were encountered:
👋🏻 Sorry for the delay on this, but with v0.5.0 (#250) this is resolved!
The GraphQL Settings have been re-worked and moved into their own "GraphQL Settings" panel on the field group settings page.
The "graphql_field_name" field is now conditional based on the state of the show_in_graphql setting. If the field group is NOT set to show_in_graphql, the graphql_field_name will not be visible, and will not be required.
If the field group IS set to show_in_graphql, the graphql_field_name is visible, and required, but is filled with a name based on the Field Group Title (but can be changed).
Hi,
First, thank you much for this amazing work.
I am using graphql to expose certain post types with some associate data to some javascript calendar component.
If I am modifying an unrelated fieldset, a layout field for example, "show in graphql " defaults to active and subsequently requires to fill "graphql field name", this has become an annoyance.
This default behavior would rather be opt-in, that you could select on general settings.
The text was updated successfully, but these errors were encountered: