You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.
Now obviously marsmallow-jsonapi can't handle the logic for all this, but it seems reasonable that this library could supply some validation. The associated Webargs project seems ideal for this.
For example, we could provide an abstract parent schema for GET query parameters, which users can inherit from, which apply some of the JSON API recommendations for these parameters.
Would this be in the scope of this project? I might have time to write a PR for this. But I wanted to sound this out first.
The text was updated successfully, but these errors were encountered:
The JSON API spec outlines a few (optional) query parameters for the requests:
include
, which determines which related resources should be includedfields[TYPE]
which includes or excludes fields from the response schemasort
, which controls sorting the responsepage
, which controls the amount of items per page and the index of the pagefilter
, which filters the response dataNow obviously marsmallow-jsonapi can't handle the logic for all this, but it seems reasonable that this library could supply some validation. The associated Webargs project seems ideal for this.
For example, we could provide an abstract parent schema for
GET
query parameters, which users can inherit from, which apply some of the JSON API recommendations for these parameters.Would this be in the scope of this project? I might have time to write a PR for this. But I wanted to sound this out first.
The text was updated successfully, but these errors were encountered: