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.
Good afternoon. In this PR, I propose introducing a new type of View for DRF. Why is it needed, and what problem does it solve?
There is ApiView, which can handle multiple HTTP methods for a single URL path, but its functionality is quite limited.
There is ViewSet, which can be used to handle multiple HTTP methods and different URL paths. However, ViewSet is rather overloaded:
I have implemented RESTView, which can do everything that a ViewSet does, but in a more explicit way and without the need for additional classes. It supports both the Django and DRF interfaces. It can be easily integrated into existing projects.
This implementation still requires more thorough testing. I would like to hear your opinion about this functionality and whether you are open to considering it for DRF. I would appreciate your feedback.