-
Notifications
You must be signed in to change notification settings - Fork 10
Conversation
export const enum NodeKind { | ||
Chain = "Chain", | ||
Metadata = "Metadata", | ||
Pallet = "Pallet", | ||
Block = "Block", | ||
StorageItem = "StorageItem", | ||
StorageMap = "StorageMap", | ||
StorageMapValue = "StorageMapValue", | ||
StorageMapKeysPage = "StorageMapKeysPage", | ||
Access = "Access", | ||
ExtrinsicFactory = "ExtrinsicFactory", | ||
Extrinsic = "Extrinsic", | ||
SignedExtrinsic = "SignedExtrinsic", | ||
Event = "Event", | ||
Read = "Read", | ||
Subscribe = "Subscribe", | ||
} |
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 thought I had rid this land of these pests!
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.
Whoops. String literals from here on out. Fingers crossed!
sign(sign: (message: Uint8Array) => Uint8Array): SignedExtrinsic { | ||
return new SignedExtrinsic(this as Extrinsic, sign); | ||
} |
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.
Needs to also take extra
and additional
I think all of these node classes should be named |
Technically, these will ultimately be effects (or at least the result of the final chained method call). Perhaps we prefix with |
I think the |
Closing in favor of #132 |
No description provided.