jfinkels

This is relevant to me. I'm the maintainer of [Flask-Restless](https://github.com/jfinkels/flask-restless) and I'd like to put together an example server configuration that uses marshmallow-jsonapi with marshmallow-sqlalchemy.

It is currently considered an error response (404 Not Found), and we aren't applying postprocessors on any error responses, only on non-error responses. It doesn't necessarily have to be that...

Hi @Datamance thanks for the report. I assume the problem comes from the behavior of trailing slashes in Flask: http://flask.pocoo.org/docs/0.12/quickstart/#variable-rules Your suggestion makes sense I suppose, let me think about...

Hi @roemhildtg, thanks for the report. Could definitely be an issue with the pagination. Can you try with the development version, or with [version 1.0.0b1](https://pypi.python.org/pypi/Flask-Restless), which I published on PyPI...

Definitely could be, Flask-Restless depends pretty heavily on primary keys in various places. I'd have to spend some time looking at an example, since I haven't tested against Postgres views...

Hi @upmauro! Thanks for the issue report. Can you provide a minimal working example (i.e. without the irrelevant columns, preprocessors, etc.) that demonstrates this bug, so that I can run...

This definitely seems to be a bug. Many-to-many relationships are basically untested in the development version of Flask-Restless right now. See also issue #480. I will work on debugging this....

Let me clarify my question. On a request `GET /api/table_a/1`, there are two possible responses I can envision, and Flask-Restless needs to decide on which one to provide by default....

I may have a problem with that pull request, see the comment I am about to post there.

I have closed the pull request suggested by @jkehler, but I'm happy to review another one that makes the changes I suggested in the discussion there.