Hi,
I have noticed to create a Metafield on resource like Product, it is required to have the `write_products` scope.
On the other hand, Metaobjects have their own access scope `write_metaobjects` and `write_metaobjects_definitions`.
I would like to know if it is planned to also create a dedicated access scope for Metafields?
Metafields are a useful feature for Apps to extend the Shopify data model with custom fields which are natively integrated into the UI at the right place (e.g. create product) and can be maintained by the Shop owner. However, the need to have the `write_products` scope (or any other write scope) to create these Metafields will proabably prohibit many Shops from installing the App in the first place.
For how I understand it, Metafields are extensions to the data model, but not changes to the actual data (product). The change to the actual data is entirely made by the Shop owner and an App can access this metafield data in an read or write access, depending if it has the `read_products` or `write_products` access scope. But it should not be necessary for an App to have the write scope if it only wishes to create Metafields and reading their values?
I hope my intention is clear and Shopify considers to decouple the Metafield definition from the Metafield value read/write.