-
Notifications
You must be signed in to change notification settings - Fork 279
Disable Banxa ACH #5823
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable Banxa ACH #5823
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ 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".
| // | ||
| // Banxa | ||
| // | ||
|
|
||
| // Disable Banxa completely | ||
| if (params.rampPluginId === 'banxa') { | ||
| yield false | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Constraint still lets Banxa hit network
Adding yield false disables Banxa only at the constraint level, but the Banxa plugin’s checkSupport and fetchQuotes both call fetchProviderConfig() before validateRamp* is invoked. With Banxa supposed to be offline, these calls still hit Banxa’s APIs and will throw, and useRampQuotes surfaces those errors to the user even though the provider is meant to be disabled. The constraint should short‑circuit before any network work or the plugin should be omitted entirely so that disabling Banxa does not keep producing visible errors or network traffic.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the current change, Banxa will be filtered out by supported-plugins before quotes run, so no Banxa errors are shown to the user.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't the ask to only disable ACH for banxa not banxa completely?
| // | ||
| // Banxa | ||
| // | ||
|
|
||
| // Disable Banxa completely | ||
| if (params.rampPluginId === 'banxa') { | ||
| yield false | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't the ask to only disable ACH for banxa not banxa completely?
|
Yep, verified that the task is only to disable ACH due to bank workflow issues |
src/plugins/ramps/rampConstraints.ts
Outdated
| // Banxa | ||
| // | ||
|
|
||
| // Disable Banxa completely |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change comment to reflect the fixup!
2412adf to
797b21d
Compare
CHANGELOG
Does this branch warrant an entry to the CHANGELOG?
Dependencies
noneRequirements
If you have made any visual changes to the GUI. Make sure you have:
Note
Disables
achpayment type forbanxain ramp constraints.src/plugins/ramps/rampConstraints.ts):achpayment type via new constraint inconstraintGenerator.Written by Cursor Bugbot for commit 797b21d. This will update automatically on new commits. Configure here.