Replies: 1 comment
-
100% agree, as this would also allow pass-thru of attributes added by themes, other apps, etc. Currently only specifying known attributes breaks across all types of integrations in ways that are quite confusing to merchants. Please re-prioritize this type of request - storefront integrations are currently stuck here. I know there are opinions internally on how to handle unbounded lists, so maybe it is Ideally this would apply to both cart and cart line attributes, and would allow a Cart Transform function to pull the attributes, modify [if needed] and pass them into the bundled or unbundled items. |
Beta Was this translation helpful? Give feedback.
-
Currently, on both the cart, and specific cart lines, we can access a specific property/attribute by passing a singular key (String). We can also do this for multiple using GQL aliases, and providing different keys. This can further, be made dynamic using input variables.
It would be a lovely update if we could add
attributes
(plural), e.gWhereby input is:
keys ( [String] ) | The keys of the attributes to check. Default value: []
Beta Was this translation helpful? Give feedback.
All reactions