We’re looking at migrating some gift card functionality from the rest api to the graphql api, and running into a seemingly undocumented difference in behaviors between the two.
We want to be able to create gift cards which honor the stores’s global gift card expiration setting as specified here:
When creating gift cards via the rest api, if an explicit expiration date is not set, then the created resource has an expiration as defined by that global setting.
When using the graphql api to create gift cards, if an expiresOn is not set, then the gift card never expires.
This seems to simply be a gap in functionality between the two api’s, and we’re a bit stumped at how to migrate over without losing this capability.
The obvious fallback will be to simply require the users to specify that same global setting in our application as well, but this is awkward at best, and opens up to drift between these settings over time (with no way for us to subscribe to updates to that setting either).
Any ideas?