-
Notifications
You must be signed in to change notification settings - Fork 9k
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
Issue with: exclusiveMaximum/exclusiveMinimum #9013
Comments
Hi @zbuh, Looks legit, investigating... |
What actually seems to be the issue?
So the visual representation of the following keywords is correctly "maximum": 180.0,
"minimum": -180.0,
"title": "Lng",
"type": "number" More info in: https://json-schema.org/draft/2020-12/json-schema-validation.html#section-6.2 |
The issue is on It should show You can check the same link you provided, it's on the same section. You can also check how ReDoc renders it. 👀 |
Yes, the issue is with exclusive*, seems that schema validation and documentation are not coherent. |
Ahh OK, because the image in issue description and the fastapi/fastapi#9709 (comment) deals with |
@zbuh mentions that there's an inconsistency. They don't say anything about Anyway, do you need anything else from us here? |
Nope, thanks! I identified the bug and working on the bugfix |
Thanks! 🙏 |
Addressed in #9030. Will be part of next SwaggerUI release. |
@char0n It will render the above as |
shouldnt it be rendered as ]-90, 90[ ? |
Both notations are equivalent: https://en.wikipedia.org/wiki/Interval_(mathematics) Either |
got it. thanks! |
Cute! Thanks! 🙏 |
Another thing I've notice is that I forgot to handle openapi: 3.1.0
info:
version: 1.2.3
title: title
components:
schemas:
Location:
properties:
lat:
type: integer results in Addressed in #9031 |
example schema:
Generated:
Originally reported in: fastapi/fastapi#9709 (comment)
The text was updated successfully, but these errors were encountered: