add params query #969
Merged
add params query #969
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
Codecov Report
@@ Coverage Diff @@
## main #969 +/- ##
==========================================
- Coverage 59.31% 59.17% -0.15%
==========================================
Files 51 51
Lines 6229 6251 +22
==========================================
+ Hits 3695 3699 +4
- Misses 2268 2286 +18
Partials 266 266
|
alpe
approved these changes
Sep 1, 2022
| // QueryParamsResponse is the response type for the Query/Params RPC method. | ||
| message QueryParamsResponse { | ||
| // params defines the parameters of the module. | ||
| Params params = 1 [ (gogoproto.nullable) = false ]; |
|
|
||
| require.Equal(t, paramsResponse.Params.CodeUploadAccess, types.AllowNobody) | ||
| require.Equal(t, paramsResponse.Params.InstantiateDefaultPermission, types.AccessTypeNobody) | ||
| } |
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.
closes #889
Should we add legacy queries for this?