-
-
Notifications
You must be signed in to change notification settings - Fork 7k
[REQ] removing size, page and sort parameter if using x-spring-paginated option #8315
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
Labels
Comments
Indeed. Another problem is to return Page object instead of list. |
@MathiasHi would love to see this implemented! 👍 |
@amelnikoff I extracted your feature request to a separate issue #14062 and may try to find a solution for this. |
tofi86
added a commit
to goldflam-gmbh/openapi-generator
that referenced
this issue
Nov 18, 2022
… 'x-spring-paginated' (OpenAPITools#8315)
5 tasks
@MathiasHi @amelnikoff I submitted a PR for this at #14064 |
anchoret
pushed a commit
to akorolev-dev/openapi-generator
that referenced
this issue
Sep 21, 2024
… 'x-spring-paginated' (OpenAPITools#8315)
5 tasks
Hi Guys, looks like #21016 has been merged, seems like this can be closed ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I use the feature from the #5022 Pull Request. When I use the same API generation file for some other programming language as Typescript, which doesn't have a pageable type I have to add the size, page, and sort parameter. This parameter now does also appear in the spring application which I want to automatically remove when I use the option.
Describe the solution you'd like
I want to check if there are defined size, page, and sort parameters in the generation file if the x-spring-paginated option is used. If this is the case I'll remove it in the spring application, so only the pageable type is used.
Additional context
I already have helped on #5022.
Please give me feedback so I know that it is ok to fork this project and create a new Pull request with this feature.
The text was updated successfully, but these errors were encountered: