Add Customer Account EXAF address types#4513
Open
marcelobarreto wants to merge 1 commit into
Open
Conversation
marcelobarreto
force-pushed
the
ae-customer-account-exaf-addresses
branch
from
89b9d7b to
e4026e9
Compare
marcelobarreto
force-pushed
the
ae-customer-account-exaf-addresses
branch
from
e4026e9 to
c2cd1cc
Compare
marcelobarreto
force-pushed
the
ae-customer-account-exaf-addresses
branch
from
c2cd1cc to
d3b8531
Compare
Expose structured extended address fields and address codes on the Customer Account mailing address API so public extension types and reference docs match the runtime data provided by Customer Account Web. Co-authored-by: GPT-5.5 <noreply@openai.com> Orchestrated-by: ae <noreply@shopify.com> Assisted-By: devx/57a4acef-c0db-4da2-b426-7ee2122c2357
marcelobarreto
force-pushed
the
ae-customer-account-exaf-addresses
branch
from
d3b8531 to
d496232
Compare
andrewmcgov
requested changes
Jul 7, 2026
|
|
||
| `; | ||
|
|
||
| const addCustomerAccountMailingAddressDocs = async (generatedDocsV2Path) => { |
Contributor
There was a problem hiding this comment.
I don't think we should need to make any changes to this script just for this API. It feels like we are solving the problem at the wrong layer here.
Still investigating the best way to avoid this, but I think we need a different approach here
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Customer Account order address APIs are gaining structured EXAF address data in Customer Account Web. Public extension types and generated reference docs need to expose the same
extendedFieldsandaddressCodefields for extension developers.Approach
AddressExtendedFieldsand structured address fields to Customer AccountMailingAddressextendedFieldsandaddressCodenullability in source comments and generated docs@shopify/ui-extensions2026-07-rcMailingAddressdocs include Customer Account-only structured fields despite the existing checkout component type-name collisionRelated World runtime PR: https://github.com/shop/world/pull/862025
Related World authorization PR: https://github.com/shop/world/pull/825328
Related issue: https://github.com/shop/issues-addresses/issues/937
Co-authored-by: GPT-5.5 noreply@openai.com
Orchestrated-by: ae noreply@shopify.com