Repository navigation
refactor(customers): reuse the expected activity enums on the business info types - #1152
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
Contributor
 |
shreyav
force-pushed
the
named-enums-account-info
branch
from
October 9, 2026 17:20
3fb5777 to
ca389b2
Compare
shreyav
force-pushed
the
named-enums-customers
branch
from
October 9, 2026 17:20
c9e175d to
fa1f658
Compare
shreyav
changed the title
shreyav
marked this pull request as draft
October 9, 2026 17:20
shreyav
marked this pull request as ready for review
October 9, 2026 18:21
AaryamanBhute
previously approved these changes
Oct 9, 2026
shreyav
force-pushed
the
named-enums-account-info
branch
from
October 9, 2026 18:35
ca389b2 to
c400b37
Compare
shreyav
force-pushed
the
named-enums-customers
branch
from
October 9, 2026 18:35
fa1f658 to
9bc7cd0
Compare
…s info types The expectedMonthlyTransactionCount and expectedMonthlyTransactionVolume fields on BusinessInfo, BusinessInfoResponse, BusinessInfoUpdate, and ExpectedActivityVolumes repeated their values inline. They now reference the ExpectedMonthlyTransactionCount and ExpectedMonthlyTransactionVolume schemas that already existed. The wire format is unchanged. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MYijrrgsrFLJZ5fkmC5XwJ
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
shreyav
force-pushed
the
named-enums-customers
branch
from
October 9, 2026 20:20
9bc7cd0 to
e9f6ef8
Compare
carsonp6
approved these changes
Oct 9, 2026
This branch was successfully deployed
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.
Independent PR on
main.What changed
expectedMonthlyTransactionCountandexpectedMonthlyTransactionVolumefields onBusinessInfo,BusinessInfoResponse,BusinessInfoUpdate, andExpectedActivityVolumesnow referenceExpectedMonthlyTransactionCountandExpectedMonthlyTransactionVolume. Those schemas already existed; the four types repeated their values inline.openapi.yamlandmintlify/openapi.yamlwithmake build.SDK impact
The wire format is unchanged. In statically typed SDKs the two business info fields change from string to enum, which can require source changes for a consumer that creates business customers.
Test plan
make lint-openapi: Redocly reports the description valid, Spectral exits 0.oasdiff breakingagainstmain: no breaking changes.🤖 Generated with Claude Code
https://claude.ai/code/session_01MYijrrgsrFLJZ5fkmC5XwJ