Why do we not have a metafieldsUnset mutation?

Private Metafields are now deprecated. Honestly, the only reason I was using them was because you could easily upsert and delete them based on “namespace” and “key”.

Now, with metafieldsSet, we can easily upsert metafields. But deleting them forces me to first query for them to get the ID, and then delete them with the ID.

Metafields are already guaranteed to be unique by their namespace & key, right? Why are we not able to delete by those two parameters?

I am constantly hitting API limits as I am forced to query metafield IDs when I need to delete them. I usually have to query thousands of them at some point.

A “metafieldsUnset” mutation would be lovely, where we can delete multiple metafields by namespace & key & ownerId.

Thank you for the detailed feedback! I have passed this along to the product team!

Seems this has been added since 2024-04. Thank you @lizk !