Bug: correctly handle denoms with / in pcli tx lp
#4766
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
The parsing looked for the first occurrence of the slash for nX@nY/fee but if X or Y contains a slash, this will be incorrect. This fixes this somewhat, by looking for the last slash, and only considering that a fee if it ends with bps. This will not correctly handle a denom containing both a slash and ending with bps, but beyond that we'll need to change the format probably.
aubrika
approved these changes
Jul 25, 2024
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.
The parsing looked for the first occurrence of the slash for
nX@nY/fee
but if X or Y contains a slash, this will be incorrect.
This fixes this somewhat, by looking for the last slash, and only considering that a fee if it ends with bps.
This will not correctly handle a denom containing both a slash and ending with bps, but beyond that we'll need to change the format probably.
Issue ticket number and link
Checklist before requesting a review
If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: