-
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
Implement Protobuf Msg Services #7540
Milestone
Comments
do-not-edit-start-codetree-epic-issuesIssues in this epic:
do-not-edit-end-codetree-epic-issues |
clevinson
changed the title
[Codetree Trial] Implement Protobuf Msg Services
Implement Protobuf Msg Services
Oct 19, 2020
16 tasks
Note that we probably don't need all the checkboxes when we're using epics @clevinson |
🎉 |
9 tasks
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Implement ADR 031: Protobuf Msg Services as documented in #7458 and #7122 .
Roadmap
RegisterQueryService
->RegisterServices
and createConfigurator
typeServiceMsg
,MsgRequest
, and router for aMsg
service
intestdata
. Router should also handleEventManager
stuffservice
request type names (we want to use the existingMsg
types without theRequest
suffix)WrapServiceResult(proto.Message, error) (*sdk.Result, error)
func which takes a service method result and error and wraps it in an*sdk.Result
orerror
for use in refactored module handlersMsgServer
toConfigurator
and wire up modulesMsg
s. See Implementation Notes belowImplementation Notes
Modules
service
definition calledMsg
in each module's tx.proto file. Re-use the existingMsg
types for the request type and add an uniqueResponse
type for eachrpc
method.MsgServer
interfacebecomes:
MsgService
methods. Ex:MsgServer
inRegisterServices
(if possible - that functionality is currently not ready, so skip this step for now)The text was updated successfully, but these errors were encountered: