Adding pagination to viewsets #9496
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At the moment, it is not possible to use response pagination with ViewSets, and it is necessary to inherit GenericAPIView. However, the concept of ViewSets is to create only what is necessary and inheriting another class, receiving other methods that may be unnecessary in this context, just to use an attribute does not match this and it also decreases performance, since some data may be cached.
Example of paginated return of action in the current ViewSet structure:
With my suggestion, we can perform pagination in the ViewSet, without the need to inherit other classes and their methods.
Example of paginated return of action in the proposed ViewSet structure: