We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
There has been some demand on this particular feature.
Example:
Resource { name ChildResource[] } GET /api/resource { name: 'foo', childResources: [1,2,3 ... 30 ] // paginated }
I'm really not sure how / if we can pull this out but I'm opening this issue to keep track of ideas suggestions.
About the configuration we could use @ApiProperty(attributes={"paginate": true}) with maybe some more parameters to control that pagination?
@ApiProperty(attributes={"paginate": true})
We may also flag this as a "wontfix" and propose an alternative solution.
The text was updated successfully, but these errors were encountered:
From #1083, it seems we need to allow greater control, at least the following should be supported:
Sorry, something went wrong.
superseeded by #2706
No branches or pull requests
There has been some demand on this particular feature.
Example:
I'm really not sure how / if we can pull this out but I'm opening this issue to keep track of ideas suggestions.
About the configuration we could use
@ApiProperty(attributes={"paginate": true})
with maybe some more parameters to control that pagination?We may also flag this as a "wontfix" and propose an alternative solution.
The text was updated successfully, but these errors were encountered: