This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non product and collection metafields? #32071
Comments
Do you know if these global metafields are available through the admin API? We currently pull down metafields for products, product variants, and collections. Within Gatsby these each have their own types, but they also implement a common interface which is what allows them to be retrieved by |
@sslotsky Ah okay, thanks, that makes sense. I'm assuming that the metafields I'm referring to are available through the Admin API as From the docs, the complete list of Types that return metafields are Collection.metafield |
I'll have to double check this but my recollection is that we couldn't get the |
You're welcome. And the Admin API can still be pinged separately in |
It certainly can. We are just cautious about having more than one way to source the data without at least understanding your use cases first. The logic to consume the regular admin API vs the bulk API is quite different. |
Thanks, I think my use-case is way too specific to make that worthwhile. In most cases with a headless shop, shop-owner-configurable site-wide settings can be handled via a CMS. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Is there already, or will there at some point be access to all types of metafields? For example, I use an app called Custom Fields by Bonify and they offer a global metafield section. I like it because it allows for arrays of product or metafield references (JSON stringified array of handles) which are really simple for the client.
Searching through
allShopifyMetafieldInterface
, I don't see the global metafields I've created, so am just wondering if they are limited to products and collections for now.As a use-case, I think globals would be really nice for certain types of site configuration with headless shops.
Cheers!
The text was updated successfully, but these errors were encountered: