-
Notifications
You must be signed in to change notification settings - Fork 78
Export Display trait on errors #1021
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
thunderbiscuit
wants to merge
2
commits into
bitcoindevkit:master
Choose a base branch
from
thunderbiscuit:feat/better-errors
base: master
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
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
58 changes: 58 additions & 0 deletions
58
bdk-android/lib/src/androidTest/kotlin/org/bitcoindevkit/ErrorsTest.kt
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,58 @@ | ||
| package org.bitcoindevkit | ||
|
|
||
| import androidx.test.ext.junit.runners.AndroidJUnit4 | ||
| import org.junit.runner.RunWith | ||
| import kotlin.test.Test | ||
| import kotlin.test.assertEquals | ||
| import kotlin.test.assertFailsWith | ||
|
|
||
| @RunWith(AndroidJUnit4::class) | ||
| class ErrorsTest { | ||
| @Test | ||
| fun bip39ErrorDisplaysBadWordCount() { | ||
| val thirteenWordMnemonic = "awesome awesome awesome awesome awesome awesome awesome awesome awesome awesome awesome awesome awesome" | ||
|
|
||
| // Building a Mnemonic fails with BadWordCount exception | ||
| val exception = assertFailsWith<Bip39Exception.BadWordCount> { | ||
| Mnemonic.fromString(thirteenWordMnemonic) | ||
| } | ||
|
|
||
| // The toString() method on the exception is the Display trait exported from Rust | ||
| assertEquals( | ||
| expected = "the word count 13 is not supported", | ||
| actual = exception.toString() | ||
| ) | ||
|
|
||
| // The exception contains a field `wordCount` correctly populated | ||
| assertEquals( | ||
| expected = 13uL, | ||
| actual = exception.wordCount | ||
| ) | ||
|
|
||
| // The `message` field on the exception is the concatenation of all fields on the type | ||
| assertEquals( | ||
| expected = "wordCount=13", | ||
| actual = exception.message | ||
| ) | ||
| } | ||
|
|
||
| @Test | ||
| fun bip32ErrorDisplaysInvalidChildNumberFormat() { | ||
| // A derivation path cannot contain words and fails with an InvalidChildNumberFormat exception | ||
| val exception = assertFailsWith<Bip32Exception.InvalidChildNumberFormat> { | ||
| DerivationPath("invalid/path/string") | ||
| } | ||
|
|
||
| // The toString() method on the exception is the Display trait exported from Rust | ||
| assertEquals( | ||
| expected = "invalid format for child number", | ||
| actual = exception.toString() | ||
| ) | ||
|
|
||
| // The `message` field on the exception is the concatenation of all fields on the type (in this case none) | ||
| assertEquals( | ||
| expected = "", | ||
| actual = exception.message | ||
| ) | ||
| } | ||
| } |
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.
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.
Since the PR title/changelog describe exporting
Displayon errors broadly, should this export be applied to the otheruniffi::Errorenums in this file too, or should the PR scope be narrowed toCreateWithPersistErroronly? Right now this is the only error type gettingDebug/Displayexported to the bindings.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.
Yep I should add it for all errors! Initially I just wanted to open this up for discussion and write up the PR description going into details. But now I'm ready to add it everywhere and will push to this PR soon.
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.
Thanks for updating this to cover the other error enums too, that addresses the scope question from my earlier review.
One follow-up question: should this PR add at least one binding-facing test/example for the generated error display behavior? Since the PR description calls out different downstream behavior in Kotlin and Swift, it may be useful to assert one representative error path so we know the exported Display/Debug behavior stays covered.
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.
That's a great idea. Let me add a few tests right now.
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.
Thanks for updating this to cover the other error enums too. That addresses my scope question.