Render OpenAPI Schema with Swagger UI#427
Conversation
modern support for generating OpenAPI Schema
excluded get_transient legacy endpoint due to plans for removal
…erializers avoid incorrect output by drf-spectacular
|
Please use a code linter like flake8 and autopep8 in your IDE so we don't have to make commits like cfb5d4e. |
|
Are the new serializer functions like |
|
They are independent. I introduced the nested serializers to address warnings with the drf-spectacular module that were occurring due to the default name for nested serializers simply being 'NestedSerializer' leading to conflict and incorrect output on swagger-ui. That being said these aren't strictly necessary, as without them swagger ui would not display nested serializers properly which may be acceptable for our usage of it. |
|
If I checkout commit cfb5d4e and then revert We need to carefully review these messages and improve the API itself based on them. For example, the messages related to @Abh1ramManugur1 until we have a chance to carefully analyze these Nested classes, this will need to stay in draft mode.
|
The only problem the nested serializers attempted to solve was the naming issue, which can be similarly solved by just reordering the serializer class definitions and calling them directly. Added extra StatusSerializer for TaskRegisterSerializer




Closes #418
Incorporated new drf-spectacular module to render OpenAPI Spec, as a result new nested serializers had to be added to serializers.py
Extended schema to incorporate view functions not automatically caught by drf-spectacular, excluded transient get legacy endpoint