Fix shortenAddress function validator #100
Open
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
MelodyFish
requested review from
LeoHChen,
samfairbairn,
allenchuang,
SoYoung210 and
DonFungible
as code owners
|
@MelodyFish is attempting to deploy a commit to the Story Protocol Team on Vercel. A member of the Team first needs to authorize it. |
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.
Hi @SoYoung210 , I want to discuss the closed PR with you.
In this
shortenAddressfunction, is it reasonable to throw an exception if the' address' params do not conform to the address type format? I think it is necessary to check the rationality of theaddressparams. Is there any other way? For example, return an empty string when the address format is wrong