Removing the JobID message cleans up the messages and related code a bit. Schema clients previously needed code like:
jobid := JobID.Value
...which I didn't like looking at :)
This also allows the request/response message types to grow in the future, without worrying about whether that field belongs on a "JobID" message. And it's a more consistent pattern. Most RPC endpoints have an EndpointNameRequest message and an EnpointNameResponse message.
geoffjentry
commented
7 years ago
Removing the JobID message cleans up the messages and related code a bit. Schema clients previously needed code like:
...which I didn't like looking at :)
This also allows the request/response message types to grow in the future, without worrying about whether that field belongs on a "JobID" message. And it's a more consistent pattern. Most RPC endpoints have an EndpointNameRequest message and an EnpointNameResponse message.