-
Notifications
You must be signed in to change notification settings - Fork 25
fix(ui): read SwapKit's error codes on the DEX amount screens #1087
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
Open
romchornyi
wants to merge
2
commits into
develop
Choose a base branch
from
fix/swapkit-error-mapping
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
🟡 Suggestion: Add regression tests for the new SwapKit error normalization
This bug fix introduces several interacting parsing and classification rules without executable coverage. Extend the existing SwapKit tests with compile-ready cases for provider code/detail composition, code-only and detail-only responses, whitespace and nil handling, code-first top-level decoding, case-insensitive
AmountTooSmallandAmountTooLowsuffixes, the four newly mapped codes, unknown-code fallback, and routability outcomes for explicit below-minimum versus ambiguousnoRoutesFoundresponses. These tests are needed to prevent a decoder or mapper refactor from dropping the stable code behind provider prose again.source: ['claude', 'codex']
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.
Added in 46ebf78 — a
SwapKitErrorCopyTestscase alongside the existing decoding tests, 12 methods covering: code-before-prose composition and its code-only / detail-only / blank / nil fallbacks; the case-insensitiveAmountTooSmall/AmountTooLowsuffix family, including the composed"<code>: <detail>"form and a negative forinboundFeeTooLow;isNoRouteon both forms; the four newly mapped codes;memoTooLongForSourceChainsharing the local memo copy; detail-after-code not changing the mapping; unknown and empty falling back to generic.The anchor case is the regression itself:
message(for: "No routes found for DASH.DASH -> BTC.BTC")must still be generic. The fix is that callers stopped sending prose alone, not that the mapper started guessing from text — a test asserting the prose maps would cement exactly the wrong behaviour.Two limits worth stating plainly:
../platformcheckout it takes SwiftDashSDK from sits on a side branch that predates several symbolsdevelopneeds (ManagedPlatformWallet.ParsedIdentityUpdateTransition,PlatformWalletManager.trackedMasternodes,MasternodeKeyRole), andDashWalletTests/DashConnect/PlatformDashConnectDataSourceTests.swiftreferences the first of those directly. That is unrelated to this PR and pre-dates it. To get a real signal I extractedSwapKitErrorCopyverbatim into a standalone target with stubbedSwapKitProviderError/SwapCryptoCurrency/DWLoggerand ran the same 28 assertions these tests encode — all pass. Whoever has an up-to-date../platformshould run the XCTest cases before merge.routability(from:)anddecodeQuoteError(from:)are private, and reaching them would mean widening the access of a private nested enum and a method purely for tests. Every rule they depend on (providerErrorMessage,isNoRoute,isBelowMinimum, code-prefix extraction) is tested directly, so a refactor that puts prose back in front of the code fails here. Say the word if you would rather have them internal and asserted end-to-end.