feat: add REGISTRATION_ADDRESS to CustomerInfoFieldName#694
Closed
ls-bolt[bot] wants to merge 1 commit into
Closed
feat: add REGISTRATION_ADDRESS to CustomerInfoFieldName#694ls-bolt[bot] wants to merge 1 commit into
ls-bolt[bot] wants to merge 1 commit into
Conversation
Adds REGISTRATION_ADDRESS as a customer/counterparty info field name so a business sender's registration address can be represented and forwarded as sender info (it already exists as a requestable counterparty data field but had no CustomerInfoFieldName member). Regenerated the bundled spec.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
3 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
Adds
REGISTRATION_ADDRESSto theCustomerInfoFieldNameenum.REGISTRATION_ADDRESSalready exists as a requestable counterparty data field, but there was no matchingCustomerInfoFieldNamevalue — so a business sender's registration address, when requested and on file, could not be represented as sender customer info. Adding the value lets it be carried through the quote/sender-info path like other counterparty fields (e.g.POSTAL_ADDRESS).Changes
openapi/components/schemas/customers/CustomerInfoFieldName.yaml— addREGISTRATION_ADDRESSopenapi.yaml,mintlify/openapi.yaml(viamake build)Additive, backward-compatible enum addition.
make lint-openapipasses (no new findings).Requested by @JasonCWang