Supporting content-negotiation (return based on content-type)

[zedrdave]

Any idea how to add content-negotiation to an endpoint, in a way similar to what is described here for flask-restful: https://flask-restful.readthedocs.io/en/latest/extending.html#content-negotiation

(also: is the project still being maintained? No update in a while…)

[lafrech]

The use of json is hardcoded almost anywhere. I wanted to make that more flexible, but after a quick look, I figured it might be complicated and since I had no direct interest in the feature, I just let it go. If someone is interested in this and wants to post his findings here, he's more than welcome.

(Sorry for not answering your previous questions. The project is still maintained, we use it in several applications. I've been spending time in finalizing apispec 1.0.0 and I just released a new flask-rest-api version compliant with apispec 1.0.0. Now, we get nested schemas auto-referencing out-of-the-box, and a more stabilized code, along with a few other improvements.)