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
Got an email recently (8th of June) regarding making calls to API(s) that will be removed on the 1st of July.
The email notes that the breaking change is metafields optional namespace html.
Does anyone know what this means?
The link in the email points to this documentation. I'm guessing that it's referring to below?
As of API version 2023-10, the GraphQL Admin and Storefront APIs have made the namespace field optional when creating, updating, or querying metafields and metafield definitions. We've updated all relevant mutations and queries to accommodate this change. When an app interacts with metafields, the default namespace is the app-reserved namespace.
This update does not affect API calls that explicitly specify a namespace. However, it simplifies the process of interacting with namespaces by removing the need to provide a namespace field when the default is suitable. As a result, Apps can now create and query Metafields without the requirement of specifying a namespace.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Got an email recently (8th of June) regarding making calls to API(s) that will be removed on the 1st of July.
The email notes that the breaking change is metafields optional namespace html.
Does anyone know what this means?
The link in the email points to this documentation. I'm guessing that it's referring to below?
Is that right?
Additionally, I should be on 2024-01 so wouldn't that mean I'd be getting an error during local development or when deployed?
Beta Was this translation helpful? Give feedback.
All reactions