Giacomo Tagliabue

can you give me more information? can you give us the code that's raising the error and the full stack trace?

I would wrap the assertion in a try/except block, print the raw response text and reraise. feel free to PR :)

true, but I'd rather return 204 then, unless there is a specific reason for returning a payload?

fair points :)

@sloria if multiple schemas need to be instantiated multiple times per-request, then they will have a separate context, so no problem there?

should be fairly easy to register the view `dispatch_request` no?

yeah. maybe something like ```py class FooView(...): authorization = FooAuth() # insert some python magic here that does `self.authorization.view = self`, I am pretty sure it's possible ``` eg in...

I thought magical things are the norm in python (sqlalchemy?) :P I am fine with inlining things but it's a big change in terms of project structuring, in the sense...

depends how you use FR, if you are really high in the microservices spectrum, having every view in one file is very convenient. but if we look at our big...

not sure the colocation pattern actually gives you more expressiveness.