no 400 default response

[gsemet]

No description provided.

[coveralls]

Coverage remained the same at 88.394% when pulling 175160a on Stibbons:clean_transmute into 5ef9277 on toumorokoshi:master.

[toumorokoshi]

@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

• http://transmute-core.readthedocs.io/en/latest/context.html
• http://transmute-core.readthedocs.io/en/latest/api.html#transmutecontext

[gsemet]

Agree with the optional flag

[coveralls]

Coverage increased (+0.02%) to 88.418% when pulling 46d6428 on Stibbons:clean_transmute into 5ef9277 on toumorokoshi:master.

[toumorokoshi]

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

https://github.com/toumorokoshi/transmute-core/blob/master/transmute_core/attributes/__init__.py#L7

That gets wired into TransmuteFunction, which can then pull fields from that attributes struct and apply it to itself:

https://github.com/toumorokoshi/transmute-core/blob/master/transmute_core/function/transmute_function.py#L42

Also a unit test on this would be great!