Andrew Standley

I'm a bit ignorant on the intricacies of this still, but my naive concern is that supporting non-json encoded responses by not specifying a marshalling schema is not really supporting...

Adding the question label since we still haven't settled on an approach.

Love the idea of providing the errors under a different key; wish I'd thought of that 😄 On a separate note: the main message should really just be a generic...

Hmm, seems like that would be covered under https://marshmallow.readthedocs.io/en/stable/api_reference.html#module-marshmallow.fields since it's just standard Marshmallow behaviour. I could see adding it as a recipe might be helpful though.

@Sytten Thanks for working on this. It looks great, but I would echo the comments about wanting the no-op __init__ removed and documentation updates being needed.

I vote we fix this by simply adding a `werkzeug.exceptions.HTTPException` error handler that generates the correct 'Error' schema response if the exception if it is not handled by `Rebar.uncaught_exception_handlers` I've...

Sorry for the lack of code examples. I will try to update later. I'm not sure what dogpile's official stance is on backwards compatibility, but my two cents is that...

Hey Mike, Thanks for the insightful and detailed response. I really appreciate you taking the time to school my naive butt :p Given the state of 'cache_on_arguements' with all it...

I would be happy to help with these issues.

+1 for GUARDIAN_FALLBACK_TO_MODEL. Per the discussion on #49 I think that setting might would also work well to control whether the ObjectPermissionBackend was explicit or not.