-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[Epic]: ValidateBasic #15648
Comments
@tac0turtle Is it changing the sdk.Msg interface( i.e deleting the validate basic from it) and adding the validate basic function in the msg server? |
Validate basic would move to the message server. No need for another validate basic function. It can be within the message function. |
@tac0turtle I didn't get you |
the checking in validate basic will get moved to the message server. |
## Description ref: #15648 --- ### Author Checklist *All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.* I have... * [ ] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title * [ ] added `!` to the type prefix if API or client breaking change * [ ] targeted the correct branch (see [PR Targeting](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#pr-targeting)) * [ ] provided a link to the relevant issue or specification * [ ] followed the guidelines for [building modules](https://github.com/cosmos/cosmos-sdk/blob/main/docs/docs/building-modules) * [ ] included the necessary unit and integration [tests](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#testing) * [ ] added a changelog entry to `CHANGELOG.md` * [ ] included comments for [documenting Go code](https://blog.golang.org/godoc) * [ ] updated the relevant documentation or specification * [ ] reviewed "Files changed" and left comments if necessary * [ ] confirmed all CI checks have passed ### Reviewers Checklist *All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.* I have... * [ ] confirmed the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title * [ ] confirmed `!` in the type prefix if API or client breaking change * [ ] confirmed all author checklist items have been addressed * [ ] reviewed state machine logic * [ ] reviewed API design and naming * [ ] reviewed documentation is accurate * [ ] reviewed tests and test coverage * [ ] manually tested (if applicable)
|
Summary
in rfc 001 we accepted the optionality of validatebasic. Within the cosmos sdk we will remove the usage of validate basic in favour of having all validation happen on msg server. We will still support an extension interface for those that would like to continue using validate basic.
Work Breakdown
ValidateBasic
logic tomsgServer
#15786ValidateBasic
logic tomsgServer
#15754ValidateBasic
logic tomsgServer
#15751ValidateBasic
logic tomsgServer
#15758ValidateBasic
logic tomsgServer
#15755ValidateBasic
logic tomsgServer
#15753ValidateBasic
to msg server #15832ValidateBasic
logic tomsgServer
#15785ValidateBasic
logic tomsgServer
#15760ValidateBasic
logic tomsgServer
#15759paramsN/AValidateBasic
logic tomsgServer
#15793ValidateBasic
logic tomsgServer
#15752The text was updated successfully, but these errors were encountered: