OpenAPI Schemas when request/response objects differ

When constructing an OpenAPI schema for a ModelViewSet, drf-spectacular has particular difficulty when a serializer field treats request/response data differently. An example of this is LearningResource.topics: Responses serializer topics as objects, but requests (assuming #34 is merged) expect integer topic ids or objects:

// GET /api/v1/learningpaths/39/
{
  "id": 39,
  "topics": [
      { "id": 15, "name": "Systems Engineering" },
      { "id": 12, "name": "Physics" }
  ]
  // ...
}
// POST /api/v1/learningpaths/
{
  "topics": [15, 12] // Or objects, though IDs are seem convenient
}

Issue: But drf-spectacular reports topics as an object in both cases.

Start at the LearningResource.topics serializer used by the ModelViewSet and inspect how drf-spectacular generates request and response schemas. Compare the generated OpenAPI document for POST and GET /api/v1/learningpaths/; done when the request documents the stated topic input while responses retain object forms.