Error for page that do not have an explicit page size set.

Created on 26 May 2023, over 1 year ago

Problem/Motivation

The change in Allow wildcard path matching Fixed seems to break requests with a page[limit] query string parameter for paths that do not have an explicit maximum page size set. I get the following error in that case:

The page size needs to be a positive integer.

Imagine you have a resource on /jsonapi/resource-name and you want to use the default max size of 50 items for this resource. But you also need a different limit for another resource and use this module for it. Then a request to /jsonapi/resource-name?page[limit]=25 will fail with the above error message.

Steps to reproduce

TBD

Proposed resolution

TBD

Remaining tasks

- Find solution
- Create MR
- Review MR
- Merge MR

User interface changes

N/A

API changes

N/A

Data model changes

N/A

🐛 Bug report
Status

Active

Version

1.0

Component

Code

Created by

🇳🇱Netherlands ricovandevin

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024