fix: query special characters #181
Merged
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
emidev98
force-pushed
the
fix/query/special/chars
branch
2 times, most recently
from
a96634d to
25ea446
Compare
|
Label the old endpoint |
emidev98
force-pushed
the
fix/query/special/chars
branch
from
25ea446 to
6b9cba0
Compare
javiersuweijie
approved these changes
May 4, 2023
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.
This pull request modify the QueryServer to allow url encoded values as for denoms to query alliances, that way we do not need special REST APIs for ibc denoms, token factory or other denoms with possible special characters.
Includes breaking changesGET:/terra/alliances/ibc/{denom}endpoint to be replaced by e.g.:GET:/terra/alliances/ibc%2Falliance2Issue #180