Question while working with PR.

Thedocumentation says: “Support for generating default schemas will be moved to a separate package and then removed”. For this PR, should we remove coreapi and everything related to it, or all code related to the wholerest_framework/schemas/ package?

If you need to remove everything related to schemas from theRest Framework, you can remove most of the code, tests, etc. in/schemas. What do you team think about this?

@auvipy I'm sorry if the tags are annoying. But this is the only place we can make design decisions about PR, and I'd love to hear your thoughts on what I should do..

yes please fix the merge conflicts as we have to remove it

I guess this is where we need to make a decision on where we stop supporting it... For example, should we remove all schema-related references in rest_framework.settings since schema generation will stop?

The documentation certainly mentions that we will be removing API documentation, but I'm confused if removing all code likeschemas.utils orrenderers.CoreJSONRenderer is included in this scope.

For example, the APIView class defaults to the DefaultSchema() class that was included in the schema package.

If we were to remove schema generation, would it be right to remove these codes as well?