-
-
Notifications
You must be signed in to change notification settings - Fork 97
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
Feat: refactor to enable additional bridge #210
Feat: refactor to enable additional bridge #210
Conversation
How does this relate to #198? |
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.
These changes look very useful, thanks for tackling this work.
I left a couple of questions / comments on the implementation, but it overall looks good
Due to either bridgeOptions or bridgeUrl is not part of account data, it should be removed to remain the bridge configurated by itself but not depend on account Remove deserializeData and serializeData due to same reason Change bridgeUrl to be a object of configuration
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.
Just a small comment, looks good for the rest!
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.
LGTM!
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.
LGTM!
@cryptodev-2s @mikesposito can you merge for me, i dont have the permission to do so |
1603ab3
- BREAKING: `LedgerIframeBridge` class constructor now takes an options object with `bridgeUrl`. - BREAKING: `LedgerBridge` `init` function now takes no parameters. - BREAKING: `LedgerBridgeKeyringOptions` no longer contain `bridgeUrl`. - BREAKING: `LedgerBridge` interface is now parameterized over its option type - Add `getOptions` and `setOptions` methods to `LedgerBridge` interface
Ledger is a hardware wallet that support multiple type of integration, it can be integrate by web or by mobile (thought bluetooth)
The current eth-ledger-bridge-keyring is only support web base by using iframe, and the class LedgerKeyring is hardcoded the bridge URL to be passed to lower level bridge
Hence, this PR is focus on enable multi bridge to be integrated into ledger keyring, and moving the bridge specific configuration/parameter into the bridge itself, thus to make the ledger keyring unify