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
I have recently added support for ExclusiveMinimum/ExclusiveMaximum for Swashbuckle a C# library that uses Swagger-ui under the hood. It uses it and it provides a OpenApi document with the version 3.0.1. I do not know if the fields ExclusiveMinimum or ExclusiveMaximum have changed from the version 3.0.1, but with my PR the library now puts the values as a boolean value
When doing the request with a parameter that has a Maximum or Minimum with the exclusive value does not prevent me from doing it.
I have also test outside of the boundary and the page is preventing me from doing it.
The text was updated successfully, but these errors were encountered:
jgarciadelanoceda
changed the title
Is IsMaximum/MinimumExclusive checked when creating the request
Is ExclusiveMinimum/ExclusiveMaximum checked when creating the request
Jun 20, 2024
I have recently added support for ExclusiveMinimum/ExclusiveMaximum for Swashbuckle a C# library that uses Swagger-ui under the hood. It uses it and it provides a OpenApi document with the version 3.0.1. I do not know if the fields ExclusiveMinimum or ExclusiveMaximum have changed from the version 3.0.1, but with my PR the library now puts the values as a boolean value
When doing the request with a parameter that has a Maximum or Minimum with the exclusive value does not prevent me from doing it.
I have also test outside of the boundary and the page is preventing me from doing it.
The related issue:
domaindrivendev/Swashbuckle.AspNetCore#2957
The text was updated successfully, but these errors were encountered: