-
Notifications
You must be signed in to change notification settings - Fork 524
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
Existing types cleanup + more api methods onto new request method #857
Conversation
- getPaymentChannel() now uses this.request() - getSettings() now uses this.request() - getLedger() now uses this.request() - transaction types cleaned up a bit, but still some work left to do - lots of other type cleanup as well
@@ -0,0 +1,56 @@ | |||
import {SignerEntry} from './index' | |||
|
|||
export type PayChannelLedgerEntry = { |
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.
Why use type
here instead of interface
?
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.
@sublimator is right, that's a left over from Flow. Changing to interface...
Might be a leftover from Flow syntax :)
|
@sublimator is right, that's a left over from Flow. Changing to interface... |
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.
I looked into all the TODOs and while I've learned some things, I don't have resolutions for them yet. We will be adding to the documentation soon, though :)
Meanwhile I think this is safe to merge. I did a couple manual tests and it worked.
ledger/types.ts
,ledger/transaction-types.ts
, etc.) cleaned up, but not yet completely moved to new system/cc @intelliot