-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Resolve Web UI Beta Testing Bugs #7471
Conversation
DepositDataResponse accounts_created = 2; | ||
} | ||
|
||
message DefaultWalletResponse { |
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.
Is a new message required? This looks like WalletResponse.
@@ -18,6 +18,11 @@ service Wallet { | |||
body: "*" | |||
}; | |||
} | |||
rpc DefaultWalletPath(google.protobuf.Empty) returns (DefaultWalletResponse) { |
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.
rpc DefaultWalletPath(google.protobuf.Empty) returns (DefaultWalletResponse) { | |
rpc DefaultWallet(google.protobuf.Empty) returns (WalletResponse) { |
I think the "Path" part doesn't align with the path. Also, can you use WalletResponse
?
That seems to make more sense to me.
@@ -18,6 +18,11 @@ service Wallet { | |||
body: "*" | |||
}; | |||
} | |||
rpc DefaultWalletPath(google.protobuf.Empty) returns (DefaultWalletResponse) { | |||
option (google.api.http) = { | |||
get: "/v2/validator/wallet/default", |
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.
get: "/v2/validator/wallet/default", | |
get: "/v2/validator/wallet/config/default", |
Recommend: add config to the path for clarity.
I was thinking that /v2/validator/wallet
would return a default wallet, so the distinction wasn't very clear between those two API routes.
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
Discussed offline that API changes / refactoring can be done in a follow up PR.
If you create a tracking issue, please link to this PR. Thanks!
Codecov Report
@@ Coverage Diff @@
## master #7471 +/- ##
=======================================
Coverage 61.11% 61.11%
=======================================
Files 427 427
Lines 31054 31054
=======================================
Hits 18979 18979
Misses 9023 9023
Partials 3052 3052 |
What type of PR is this?
What does this PR do? Why is it needed?
Which issues(s) does this PR fix?
Other notes for review
Diff large due to mocks