-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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 ADR 031: Protobuf Msg Services #7500
Labels
Milestone
Comments
aaronc
added
T: Client UX
T: Dev UX
UX for SDK developers (i.e. how to call our code)
labels
Oct 9, 2020
I’m inclined to start on this ASAP. If we get this done pretty quickly clients won’t get too used to the existing API so that we have backwards compatibility concerns. Maybe this could even be part of a quick v0.40.1 in a couple of weeks. |
9 tasks
9 tasks
9 tasks
9 tasks
9 tasks
6 tasks
This was referenced Oct 14, 2020
9 tasks
9 tasks
9 tasks
Closing in favor of #7540 (Codetree Epic) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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: