cli icon indicating copy to clipboard operation
cli copied to clipboard

[Feature]: Add metafield_namespaces field in Webhooks created in shopify.app.toml

Open MathiasGr opened this issue 1 year ago • 2 comments

What area(s) will this request affect?

App, Deployment

What type of change do you want to see?

New feature

Overview

Hi there, Following the announcement that Webhooks could be set via the config now, I tried to set it up for our app, but can't manage to find where to configure metafield_namespaces for these webhook subscriptions. Would it be possible to add them to the config file setup?

Motivation

See overview.

MathiasGr avatar Jun 24 '24 18:06 MathiasGr

We would love that as well!

patjakubik avatar Jul 26 '24 09:07 patjakubik

cc: @anitameh @rebeccajfriedman

gonzaloriestra avatar Jul 30 '24 09:07 gonzaloriestra

Any updates on this? @gonzaloriestra @anitameh @rebeccajfriedman

patjakubik avatar Sep 10 '24 10:09 patjakubik

Hey all - this is a known issue and will be addressed. We are moving in a direction in which the Metafield access pattern based on namespace and key is consistent across all surfaces.

jesalerno84 avatar Oct 02 '24 15:10 jesalerno84

Much needed!

bluedge avatar Nov 07 '24 21:11 bluedge

I'd also like to see this feature implemented. What's odd is it looks like it was included in declarative webhook subscriptions and was intentionally removed: https://github.com/Shopify/cli/pull/3632#issue-2218804088

yosef-grant avatar Nov 19 '24 15:11 yosef-grant

@gonzaloriestra Why is this closed without comment? This feature seems like a glaring omission from the declarative web hook capability. Apps are encouraged to utilise metafields but cannot use the preferred route to be notified of changes to them. If it's being addressed, I don't see why the issue is being closed. And if it's not being addressed, a comment to that effect (and perhaps an explanation) would seem to be in order.

ryanolf avatar Jan 26 '25 10:01 ryanolf

@gonzaloriestra Why is this closed without comment? This feature seems like a glaring omission from the declarative web hook capability. Apps are encouraged to utilise metafields but cannot use the preferred route to be notified of changes to them. If it's being addressed, I don't see why the issue is being closed. And if it's not being addressed, a comment to that effect (and perhaps an explanation) would seem to be in order.

AFAIK it's on their internal roadmap

patjakubik avatar Jan 27 '25 12:01 patjakubik

Any news on this one?

BaggioGiacomo avatar Aug 27 '25 08:08 BaggioGiacomo