We have a custom remix app that has market-specific functionality. This app accepts proxy requests from the customers on our site…
Old way
The proxy endpoint is embedded with locale and country parameters from liquid, and called when the user presses a button.
This proxy endpoint retrieves the locale and country information from the URL parameters, since proxy endpoints in Remix apps do not include localization info in the request body
These are then used to retrieve the correct market and it’s metafields using the Storefront API to determine how the app should function
However, localization.market is now deprecated from the storefront API.
New way
I want to confirm that the new way of doing this, maintaining compatibility with Shopify’s new markets, would be as follows:
To embed the “localization.market” id from liquid into the proxy endpoint url
And then inside our proxy endpoint to use the market query of the Admin GraphQL API to retrieve the correct market and it’s metafields.
Will this way be compatible with Shopify’s new market system? Ultimately we only want the user to receive info for the market that matches the site URL they’re currently browsing (subfolder-based markets). Will liquid’s “localization.market” be sufficient to ascertain this? Must other steps be taken to assure that a user only receives info for the market that matches their current site URL, given that markets can now have multiple conditions and a User could potentially match multiple markets?