-
Notifications
You must be signed in to change notification settings - Fork 49
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
Asset: Separate preparation of creation of VC Asset from dispatch #215
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.
Please keep a newline after every method end.
assetQty, | ||
digest, | ||
creator, | ||
authorizationUri, |
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.
prepareVcExtrinsic
expects authorAccount
as a parameter after creator
, which is missing while calling the method.
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.
Done !
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.
Nitpick: A good PR should implement only focused area, and fix whitespace issues only in the related area. For fixing any other lines, either send them as a separate PR or separate commit in the same PR (ie, one PR can have multiple commits) so for reviewer, it is easier to focus on the 'logic' changes.
That practise helps in getting PRs reviewed quickly.
Ah! anyways, I see some merge conflicts here, can you rebase the whole PR ? |
Resolved the merged conflict, thank you for the feedback ! I'll keep PRs more focused in the future. |
@vatsa287 If the PR is good, can we merge it? Thanks |
fixes #213