-
Notifications
You must be signed in to change notification settings - Fork 36
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
Backport: Removal of regex usage on denom validation #570
Changes from all commits
f154204
7fc05b3
eb7034f
c1e444e
16fd60b
b9808f9
00b88c7
4fbad07
db7ea08
af52754
ba488ea
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -326,7 +326,7 @@ func (s *CLITestSuite) TestCLITxGrantAuthorization() { | |||||
fmt.Sprintf("--%s=%s", flags.FlagFees, sdk.NewCoins(sdk.NewCoin("stake", sdk.NewInt(10))).String()), | ||||||
}, | ||||||
true, | ||||||
"invalid decimal coin expression", | ||||||
"nvalid character in denomination: ", | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The error message has been modified from "invalid decimal coin expression" to "nvalid character in denomination: ". This change seems to have a typo, missing the initial "I" in "Invalid". Correcting this typo will ensure the error message is clear and accurately reflects the validation error. - "nvalid character in denomination: "
+ "Invalid character in denomination: " Committable suggestion
Suggested change
|
||||||
}, | ||||||
{ | ||||||
"Valid tx send authorization", | ||||||
|
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.
btw we should change this upstream to just be bytes, and a couple of if statements. Rune's / these unicode calls are even more complex than what we need.
e.g. imagine checking
[0-9/_]
asbyte >= 0x2F && byte <= 0x3A
.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.
Can make an issue for trying this upstream