You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{
"errors": [
{
"message": "Abstract type \"Pet\" was resolved to a type \"pet-cat\" that does not exist inside the schema.",
"path": [
"pets_by_id"
]
}
],
"data": {
"pets_by_id": null
}
}
I've tried a few combinations of the mesh.yaml, all without success:
Issue workflow progress
Progress of the issue based on the
Contributor Workflow
Github (forked from Openapi Handler - discriminator in Openapi Schema cannot be handled correctly #5413 (comment))
Describe the bug
When using a discriminator, it seems the field that does the mapping cannot have a
-
in it. For legacy APIs it's useful to be able to do so.To Reproduce Steps to reproduce the behavior:
Github
With the query
I get the error message
I've tried a few combinations of the
mesh.yaml
, all without success:or changed to
or with
title: "petCat"
andtitle: "petDog"
.Expected behaviour
While I don't want a type name with a
-
in it, it would be useful to be able to have the discriminator field to be able to do so.Environment:
and
The text was updated successfully, but these errors were encountered: