Problems with Swagger APIView #4978
Labels
APIView
Central-EngSys
This issue is owned by the Engineering System team.
Swagger
Issues for APIView support of Swagger
Here are a few problems I discovered in the Swagger APIView when reviewing PR 19233. The APIView for this PR is here.
Details
Note: The PR has been updated since the APIView was created. I think the hash for the version that was used for APIView is
4bdad89
.The enum values for $expand parameter are not shown.
The parameter definition is:
but APIView only shows the parameter type:
Still wanting diff within tables - api-version was not removed and added.
APIView does not handle inline schemas
The
ExpandedTrunk
schema defines thehealth
property with an "inline" schema (not a $ref)but APIView shows it only as
type: object
APIView does not handle allOf
For the same
ExpandedTrunk
schema of the previous item, theallOf: [ { "$ref": "#/definitions/Trunk" } ]
is not rendered in the APIViewAPIView does not handle additionalProperties with specific type (e.g. Map)
The
domains
andtrunks
properties ofExpandedSipConfiguration
are declared "Maps" -- usingadditionalProperties
-- ofDomain
andExpandedTrunk
respectively:but APIView renders these as simply
type: object
The text was updated successfully, but these errors were encountered: