no 400 default response#31
Conversation
Signed-off-by: Gaetan Semet <gaetan@xeberon.net>
c6f7258 to
175160a
Compare
|
@stibbons it's pretty guaranteed that it's possible to get a 400 response from a transmute API, as any violation of the schema will return that back as an error code. How about an optional flag in the decorator instead? Or one can do global switches by modifying either the global (or passing in a new instance) of transmutecontext |
|
Agree with the optional flag |
toumorokoshi
left a comment
There was a problem hiding this comment.
The code looks good, but I think you'll need to pipe that config through @Describe, by adding that option to TransmuteAttribute:
https://github.com/toumorokoshi/transmute-core/blob/master/transmute_core/decorators.py#L35
That gets wired into TransmuteFunction, which can then pull fields from that attributes struct and apply it to itself:
Also a unit test on this would be great!
No description provided.