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
Since 6.4.0, swagger-ui has been upgraded from v4.12.0 to v5.18.1.
Unless there's a difference in the OpenAPI document itself that causes this change in behaviour (and it's a bug), this will be something to take up with the SwaggerUI project to see if it's a bug or an intentional UX change between those versions.
Describe the bug
Clicking the "Try it out" on an operation with request body doesn't automatically trigger the "Example value" editor.
The following video contains a comparison between the expected (which I could trace back to v6.4.0, the one I was using) and the actual behavior:
Expected:
https://github.com/user-attachments/assets/95f338b0-b9b7-44e7-b2dd-08b23f1d4b29
Actual:
https://github.com/user-attachments/assets/191634b6-c446-4e26-ba85-8dff1df804bf
Expected behavior
Clicking the "Try it out" on an operation with request body automatically triggers the "Example value" editor.
Actual behavior
Clicking the "Try it out" on an operation with request body doesn't automatically trigger the "Example value" editor.
Steps to reproduce
Exception(s) (if any)
No response
Swashbuckle.AspNetCore version
v7.0.0 (current).
.NET Version
net8.0
Anything else?
No response
The text was updated successfully, but these errors were encountered: