Repository navigation
Conversation
Align messaging identifiers across TypeScript, browser and Calls
Unify session configuration and QuickLink onboarding
Replace the raw platform string on WhatsAppAccount, ProfileData, and the session.connected payload with phonePlatform and accountType, type the connected account's public id instead of lid, and repin the contracts to polymorfa/polymorfa aca849cda.
Remove the draft BanSafe snapshots; dev's canonical snapshots at 1600403db9dcf7996dbbb882375b1165859829d3 cover the same operations. Move the 35 BanSafe ledger gaps to covered, add MessagingClient.banSafe for the 10 Messaging settings routes (client tokens rejected before transport), type claim credit amounts as decimal quantities, and accept the optional nested enforcement projection on enforcement summaries.
QuickLink is a closed-source hosted page. Integrators create a link on the server with MessagingClient.quickLinks.create and send the person to the returned URL, so the browser controller, pmfa-quicklink element, ./quicklink elements subpath, and React QuickLink component are removed. Shared element and binding tests now use the message list, the examples drop QuickLink, and the ledger exclusions name the hosted page as the only consumer of the public participant routes.
feat(sdk): add typed BanSafe Health resources
Replace allowedRedirectUris with successCallbackUrl, failureCallbackUrl, and allowPhoneChange on saved QuickLink settings. Remove Customer phone, CustomerSummary phoneMasked, and pairing-link locale/theme request fields, none of which exist in the pinned management contract. Add a contract-shape test that compares these types with the snapshot schemas.
Add ContactsSyncPayload and MessageEchoPayload, register both events, and expose the optional QuickLink externalId on the webhook envelope, matching the messaging contract at API 1600403.
Refresh the pinned source revision, remove retired direct session creation from the resource list, fix stale QuickLink examples and routes, and remove Customer phone from examples.
Add Customer lifecycle, BanSafe, campaign, message.failed, and template.status payloads to the webhook catalog, and the redacted response excerpt to webhook delivery attempts. A contract test now fails when the pinned Messaging spec defines an event the catalog does not list, and validates complete fixtures against each payload schema. Closes #256 Closes #257
feat!: remove the embedded QuickLink UI
Align QuickLink settings, Customer, and Cloud webhook types with API 1600403
|
Warning Review limit reachedNext included review available in 30 minutes. View limit detailsLimit details: You’ve used all 6 included reviews currently available. Your 40 included PR review attempts over the past 7 days set your current allowance at 6 reviews per hour. The included review limit has been reached and this organization has disabled usage-based review continuation. Wait for reviews to reset or ask a billing admin to change After included review limits. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (108)
Comment |
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
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
Promotes SDK
devtomain(28 commits). This merge produces a tree identical todev.SDK
maincurrently carries the original bootstrap ledger, pinned topolymorfa/polymorfa@6918c56. Against monorepomain's current contracts it reports about 350 gaps. Themaincoverage job opens one issue per gap and stopped at 240 when GitHub rate-limited it. After this merge, SDKmainusesdev's ledger, pinned toaca849cda44ad8582d7ae87489404d2483173a53. The monorepo promotion (polymorfa/polymorfa#178) brings monorepomainto those same contract bytes. The nextmaincoverage run then finds no gaps and closes the[main] SDK coverageissues.Included since the last promotion:
devVerification
git merge-tree origin/main origin/devhas no conflicts and matches thedevtree exactly.devchanges each passed the full local gate and hosted Node 20 and 22 CI before merging.dev's ledger and feat(sdk): add typed BanSafe Health resources #8 merged, the strict coverage check reports 0 missing operations ataca849c.Five-part check
aca849c.devTypeScript packages tomain. Nothing is published to a registry.dev. Public Mintlify docs are unaffected: they cover installing the unpublished package, not SDK type names, and the API reference already documents the webhook events.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.