Conversation
Replace drf-yasg UI/schema endpoints with drf-spectacular while retaining compatibility routes. Keep drf-yasg dependency for existing annotations, convert critical custom schema bits to OAS3 (anyOf) and fix serializer edge case. This enables /api/v1/docs/?format=openapi to return a valid OpenAPI 3 schema consumable by generators (resolves #6183).
|
Cursor Agent can help with this pull request. Just |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
for more information, see https://pre-commit.ci
…le; keep schema serve auth in local
Co-authored-by: kim.gustyr <kim.gustyr@flagsmith.com>
Co-authored-by: kim.gustyr <kim.gustyr@flagsmith.com>
|
@cursor make the tests green. Use Cursor's Github app access to view test checks result. If you choose to run the tests yourself, use |
|
❌ Unable to add follow-up after multiple attempts. The agent may be experiencing issues. Please try again later or check the agent status. Learn more about Cursor Agents |
|
Okay, Cursor's background agent is unresponsive now. I want to keep this work in a background agent, so we might hold this off until we start trying Claude Code out. CC @matthewelwell |
|
Superseded by #6451. |
Thanks for submitting a PR! Please check the boxes below:
docs/if required so people know about the feature!Changes
This PR migrates the API documentation from
drf-yasgtodrf-spectacularto provide an OpenAPI 3.0 compliant schema, addressing issue #6183 and building on PR #6184.Key changes include:
drf-yasgwithdrf-spectacularfor schema generation and UI./swagger.json,/swagger.yaml, and/docs/paths.drf-spectacularsettings, including security schemes and permissions.EdgeFeatureField) to usedrf-spectacular's@extend_schema_fieldfor union types.CreateUpdateEnvironmentSerializerto guardself.instanceaccess.drf-spectaculartopyproject.toml.How did you test this code?
I tested this code manually by:
GET /api/v1/docs/?format=openapiGET /api/v1/docs/GET /api/v1/swagger.jsonGET /api/v1/swagger.yamlGET /api/v1/schema/