feat: Fix generating uuid requiring admin account and json rpc number of parameters #1666
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@antonydenyer, could you kindly help me to take a look at this PR pls? This is a fix to patch some of the remaining issues in the previous PR. |
antonydenyer
approved these changes
Aug 21, 2023
rodion-lim-partior
deleted the
fix_generate_uuid_requiring_admin_account
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are 2 issues fixed in this PR:
web3ext.goValidation on admin accounts was implicitly introduced in the previous PR when calling
GenerateTransactOptionsfunction, which is not required for generating uuid. This is now removed.