-
Notifications
You must be signed in to change notification settings - Fork 381
Response type is ignored: object instead of actual type #5377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I too am having the same issue. See the discussion post I made here If its always going to show a plain |
Hey @cyclr-adrian, Exactly. I tried using ProducesResponseTypeAttribute to explicitly let it know the response type, but it didn’t work. The document is correct, but rendering in Scalar doesn’t take models into account. It just lists model in the left panel which is useless. |
hey @luarvic @cyclr-adrian thank you both for your precious feedback! we are working on making this happen asap! |
hey @paul-datatech911, seems like there's a missing bit here! pushing an update right now |
Cool, thanks! When do packages typically get pushed out? |
packages have been released, this was part of #5627 |
@paul-datatech911 of course, glad to hear it thanks you! |
Uh oh!
There was an error while loading. Please reload this page.
What happens?
I generate an open API documentation and expose it via Scalar UI using the following NuGet packages:
The problem is that the Scalar UI ignores the schema name in the responses (i.e.
array Device[]
), and showsarray object[]
instead. Although, the actual type presents in the generated documentation (see the OpenAPI Document below).I tested the same file with the Swagger UI and it does show the correct schema.
What did you expect to happen?
I expect to see
array Device[]
instead ofarray object[]
in responses ifDevice
is referenced in the responses definition, e.g.:OpenAPI Document
The text was updated successfully, but these errors were encountered: