Skip to content

Feature: Paging and filtering on nested endpoints #751

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
bart-degreed opened this issue May 13, 2020 · 0 comments · Fixed by #792
Closed

Feature: Paging and filtering on nested endpoints #751

bart-degreed opened this issue May 13, 2020 · 0 comments · Fixed by #792

Comments

@bart-degreed
Copy link
Contributor

bart-degreed commented May 13, 2020

Due to a limitation in EF Core 3.x, there is no straight-forward way to implement support for this in JsonApiDotNetCore.

As a result, the following requests do not work:

GET /blogs/1/articles?filter[title]=like:art HTTP/1.1

Returns HTTP 400: Query string parameter 'filter[title]' is currently not supported on nested resource endpoints.

GET /blogs/1/articles?page[number]=2 HTTP/1.1

Returns HTTP 400: Query string parameter 'page[number]' is currently not supported on nested resource endpoints.

GET /blogs/1/articles?page[size]=2 HTTP/1.1

Returns HTTP 400: Query string parameter 'page[size]' is currently not supported on nested resource endpoints.

In addition to this, the configured DefaultPageSize in options is not applied on nested endpoints.

We should be able to overcome these limitations using EF Core 5, which is currently in preview. This issue tracks the work on that.

@bart-degreed bart-degreed changed the title Paging and filtering on nested endpoints Feature: Paging and filtering on nested endpoints May 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

1 participant