We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
there are many places using generic "number" as numeric type.
example:
opensearch-api-specification/spec/schemas/_core.bulk.yaml
Line 56 in 939a292
should use more accurate definition for numeric types. https://swagger.io/docs/specification/v3_0/data-models/data-types/
The text was updated successfully, but these errors were encountered:
@amberzsy Is there more than #598 and #612?
I think we need a lint rule for these.
Sorry, something went wrong.
yes probably more..... maybe let me update the ticket with scope of Search & Document API?
yes, agree. issue opened here
No branches or pull requests
What is the bug?
there are many places using generic "number" as numeric type.
How can one reproduce the bug?
example:
opensearch-api-specification/spec/schemas/_core.bulk.yaml
Line 56 in 939a292
What is the expected behavior?
should use more accurate definition for numeric types.
https://swagger.io/docs/specification/v3_0/data-models/data-types/
The text was updated successfully, but these errors were encountered: