These are chat archives for damianh/Cedar

9th
Jun 2015
Dennis Doomen
@dennisdoomen
Jun 09 2015 07:48
So how do I prevent Cedar's PutCommand to pass the fully qualified type name of the command as part of the request?
Damian Hickey
@damianh
Jun 09 2015 07:53
Will have something to show, will put in a PR and can discuss - today.
I'll summarize, the Type -> MediaType and MediaType -> Type conversion needs to be a more explicit and flexible.
Damian Hickey
@damianh
Jun 09 2015 12:58
damianh/Cedar.CommandHandling#23 @yreynhout @thefringeninja @dennisdoomen Ready for look over.
João Bragança
@thefringeninja
Jun 09 2015 13:01
not clear on server side wireup
is this going to auto register my handlers or something
Damian Hickey
@damianh
Jun 09 2015 13:02
this doesn't change the module aspect
João Bragança
@thefringeninja
Jun 09 2015 13:13
aha. it's "Command WithSyncHandler" NOT "CommandWithSync Handler"
Damian Hickey
@damianh
Jun 09 2015 13:41
I'll make it CommandThatHasASyncHandler :)
João Bragança
@thefringeninja
Jun 09 2015 13:41
ofT
Damian Hickey
@damianh
Jun 09 2015 13:43
Just noticed there isn't a way to get the collection of command types from a Module. Adding that extension now...
Damian Hickey
@damianh
Jun 09 2015 14:15
@yreynhout Just remembered why I did the customer headers, the HttpProblemDetails Type field is optional.
A thought: if a problem type uri is not specified, I can just deserialize to HttpProblemDetails, and just discard any 'extended data'
Yves Reynhout
@yreynhout
Jun 09 2015 15:27
@damianh PR looks ok to me
Damian Hickey
@damianh
Jun 09 2015 17:51
@yreynhout I'll merge it. These things only really get exercised whence consumed anyway.