-
Notifications
You must be signed in to change notification settings - Fork 14
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
Renames for readability #409
Conversation
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 few small typo things. Overall this is excellent.
common: CommonParams, | ||
needsTxSpecific: boolean, | ||
serverUri: string, | ||
txId: string |
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.
So here we have positional parameters, but above updateTransactionsSpecific
has named parameters. I'm not sure if we want to be more consistent about named / positional parameters, but I do appreciate that CommonParams
is cleaned up now.
This is just an observation. There are no changes needed unless you want to.
The processor is a DAL, so it's better to be named appropriately. All the type names will be suffixed with "Data" to distinguish them from other models of the same kind of object (e.g. TransactionData vs EdgeTransaction).
This component of the plugin makes more sense to be name "processor" because it's the component that processes data from the network and storage for the engine.
This adds documentation comments to each processor function to briefly describe the function's intent.
Trezor is known to rate limit. In the future, a mock Blockbook interface is the correct fix.
CHANGELOG
Does this branch warrant an entry to the CHANGELOG?
Dependencies
noneDescription
none