You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a small Dart-side smoke test for the generated Wallet.keychains() binding.
This is not intended to retest wallet keychain behavior owned by bdk-ffi. The goal is only to prove the regenerated Dart binding path is callable and that List<WalletKeychain> lifts into usable Dart objects. Wallet.keychains() came in through #101, and the current Dart test suite does not call this generated path today.
Scope
Call wallet.keychains() from Dart on a standard wallet.
Assert the returned list is non-empty.
Assert each returned WalletKeychain exposes a usable keychain.
Assert each returned WalletKeychain.publicDescriptor can be converted to a descriptor string.
Keep assertions thin and focused on Dart binding usability.
changed the title [-]test: add Wallet.keychains() behavior coverage for standard and single-descriptor wallets[/-][+]test: add Wallet.keychains() Dart binding smoke coverage[/+]on Jul 6, 2026
Go ahead @j-kon, I would like to see these covered:
Call wallet.keychains() from Dart on a standard wallet.
Assert the returned list is non-empty.
Assert each returned WalletKeychain exposes a usable keychain.
Assert each returned WalletKeychain.publicDescriptor can be converted to a descriptor string.
Keep assertions thin and focused on Dart binding usability.
Activity
[-]test: add Wallet.keychains() behavior coverage for standard and single-descriptor wallets[/-][+]test: add Wallet.keychains() Dart binding smoke coverage[/+]j-kon commentedon Jul 7, 2026
Hi, I’d like to work on this if it’s available.
My plan for the PR would be to keep the change very small and focused on Dart binding smoke coverage only.
Proposed approach:
Wallet.keychains().wallet.keychains()from Dart.WalletKeychainexposes a usablekeychain.WalletKeychain.publicDescriptorcan be converted to a descriptor string.bdk-ffi.Validation I would run before opening the PR:
dart format --output=none --set-exit-if-changed lib test exampledart analyze --fatal-infos --fatal-warnings lib test exampledart testIf this plan sounds good, please assign this issue to me.
Johnosezele commentedon Jul 7, 2026
Go ahead @j-kon, I would like to see these covered: