chore: [Nextiva] Add WASM for Nextiva Connector in Dashboard#4922
chore: [Nextiva] Add WASM for Nextiva Connector in Dashboard#4922shuklatushar226 wants to merge 1 commit into
Conversation
Rebuilt euclid_wasm from hyperswitch add-nextiva-connector so the Control Center recognizes the Nextiva connector (BodyKey: API access key + Account ID). The euclid.js/.d.ts line churn is wasm-bindgen export-ordering noise (same 34 exports, none added/removed); the substantive change is in euclid_bg.wasm. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Review changes with Changed Files
|
github-actions
Bot
added
the
Closed
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9ffd250069
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| export function getAllConnectors() { | ||
| try { | ||
| const retptr = wasm.__wbindgen_add_to_stack_pointer(-16); | ||
| wasm.getPayoutDescriptionCategory(retptr); | ||
| wasm.getAllConnectors(retptr); |
There was a problem hiding this comment.
When the regenerated wasm starts returning nextiva from getAllConnectors(), the rest of the Control Center still has no corresponding frontend connector type or string mapping. In the V2 connector list path, ConnectorInterfaceUtils.res:361-362 maps backend connector_name through getConnectorNameTypeFromString, but ConnectorUtils.res:1217-1219 falls through to UnknownConnector("Not known") for anything not listed, so any configured Nextiva account returned by the API is rendered/routed as an unknown connector instead of Nextiva. Please add the Nextiva enum/string/display/info/list entries alongside this wasm update.
Useful? React with 👍 / 👎.
shuklatushar226
changed the title
XyneSpaces
left a comment
XyneSpaces
left a comment
There was a problem hiding this comment.
Review Summary
Classification: WASM Bundle Regeneration — Nextiva Connector Support
Risk Level: Low
Files Changed: 4 files (generated wasm-bindgen artifacts)
Verification
Build Artifact Review:
✅ Source branch documented — Built from add-nextiva-connector branch with proper flags
✅ Export count unchanged — PR confirms same 34 exports, none added/removed
✅ Expected churn pattern — euclid.js / .d.ts changes are export-ordering noise from wasm-bindgen
✅ Substantive change confirmed — euclid_bg.wasm binary updated with Nextiva connector config
Dependency Coordination:
- This PR pairs with #4923 (dashboard registration)
- Both must merge together for the connector config form to render correctly
Findings
None. Standard WASM regeneration following documented build process.
Verdict: ✅ Routine WASM bundle update. Safe to merge alongside #4923.
2 participants
Summary
Regenerates the
euclidWebAssembly bundle so the Control Center recognizes the Nextiva connector (PayConex / Bluefin), added in hyperswitch PR #12608.Nextiva is a UCS-only connector; its dashboard auth config is
BodyKey:api_key— PayConex API access keykey1— PayConex Account IDBuilt from the
add-nextiva-connectorbranch via:Files
public/hyperswitch/wasm/euclid_bg.wasm— the substantive change (now includes Nextiva's connector config)public/hyperswitch/wasm/euclid.js,euclid.d.ts,euclid_bg.wasm.d.ts— regenerated glue🤖 Generated with Claude Code