Skip to content
This repository has been archived by the owner on Jul 23, 2024. It is now read-only.

Field settings on admin area defaulting to "Show in GraphQL" #127

Closed
foltra opened this issue Apr 20, 2020 · 1 comment
Closed

Field settings on admin area defaulting to "Show in GraphQL" #127

foltra opened this issue Apr 20, 2020 · 1 comment
Labels
Location Rules Issues related to ACF Location Rules 🚀 Actionable

Comments

@foltra
Copy link

foltra commented Apr 20, 2020

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.

@jasonbahl jasonbahl added Location Rules Issues related to ACF Location Rules 🚀 Actionable labels Mar 30, 2021
@jasonbahl jasonbahl added this to the ACF Schema Location Rules milestone Mar 30, 2021
@jasonbahl
Copy link
Contributor

👋🏻 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).

You can see this in action here: https://www.youtube.com/watch?v=VvrZGrcwv0Y

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Location Rules Issues related to ACF Location Rules 🚀 Actionable
Projects
None yet
Development

No branches or pull requests

2 participants