Describe the bug
The OpenAPI schemas do not match the responses from the API's themselves. They seem to differ in at least two ways:
- Missing root element
Each API response includes the serialized type name which is omitted from the declared schema
- Incorrect date-time formatting
API responses declare date-time fields, which are defined in OpenAPI3 to be compliant with RFC3339 §5.6 (ISO8601 style strings). API Endpoints are actually returning an object with a ticks field.
To Reproduce
Call /api/openapi.json to get schema
Call /api/users/current to get actual.
Expected behavior
Schema and actual should match
Actual behavior
Schema and actual do not match
Screenshots
Environment
Describe the bug
The OpenAPI schemas do not match the responses from the API's themselves. They seem to differ in at least two ways:
Each API response includes the serialized type name which is omitted from the declared schema
API responses declare date-time fields, which are defined in OpenAPI3 to be compliant with RFC3339 §5.6 (ISO8601 style strings). API Endpoints are actually returning an object with a ticks field.
To Reproduce
Call /api/openapi.json to get schema
Call /api/users/current to get actual.
Expected behavior
Schema and actual should match
Actual behavior
Schema and actual do not match
Screenshots
Environment