Fix deserialisation error on next_key
#112
Merged
Conversation
This file contains hidden or 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
For queries that return paginated responses the next key value can be
null
```json
{"positions":[],"pagination":{"next_key":null,"total":"0"}}
```
This leads to a deserialisation error. This fixes the issue by making
next_key optional.
The issue was first reported by @keyleu with a fix so due credit here.
osmosis-labs#104
packages/osmosis-std/src/types/cosmos/base/query/v1beta1.rs
packages/osmosis-std/src/types/cosmos/base/query/v1beta1.rs
iboss-ptk
requested changes
May 2, 2024
packages/osmosis-std/src/types/cosmos/base/query/v1beta1.rs
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.
For queries that return paginated responses the next key value can be
null
{"positions":[],"pagination":{"next_key":null,"total":"0"}}This leads to a deserialisation error. This fixes the issue by making
next_key optional.
The issue was first reported by @keyleu with a fix so due credit here.
#104