Jérôme Lafréchoux

**Comment by [tinproject](https://github.com/tinproject)** _Tuesday Sep 18, 2018 at 20:47 GMT_ ---- @andho If I remember well I had all my API inside a blueprint, sharing the Flask App with 'normal'...

Thanks for putting me on the right track. I have a Dualshock 4 as well and thanks to the instruction on [Debian Wiki](https://wiki.debian.org/Mupen64Plus) I managed to get a satisfying layout...

Thanks for investigating. I saw the failures but didn't have the time to look into it yet. Good to know it is being taken care of upstream.

It is fine. Just craft a custom name resolver to provide a different name for partial schemas. ```py def resolver(schema): # This is the default name resolver from apispec schema_cls...

I didn't test that code but I think it should work with the `partial=True` change you proposed above. It will create two schemas in the doc but you only use...

Related to #51 and #174. As I wrote in #51, the use case of API and website seems like a corner case to me. I don't mind supporting it if...

Thanks for the details. This makes sense. There might be a way to create all the exceptions dynamically from the `HttpException` subclasses. And we could make `find_exception_by_code` a classmethod. I...

I was thinking of something along the lines of exceptions.py ```py import sys module = sys.modules[__name__] for exc in ...: # Iterate over Werkzeug exceptions class Exc(exc, FlaskSmorestError): ... setattr(module,...