Open amberzsy opened 2 weeks ago
there are many places using generic "number" as numeric type.
example: https://github.com/opensearch-project/opensearch-api-specification/blob/939a292753eeb1b3bffdf5ed4f3039ab5edd2f04/spec/schemas/_core.bulk.yaml#L56
should use more accurate definition for numeric types. https://swagger.io/docs/specification/v3_0/data-models/data-types/
@amberzsy Is there more than #598 and #612?
I think we need a lint rule for these.
yes probably more..... maybe let me update the ticket with scope of Search & Document API?
yes, agree. issue opened here
What is the bug?
there are many places using generic "number" as numeric type.
How can one reproduce the bug?
example: https://github.com/opensearch-project/opensearch-api-specification/blob/939a292753eeb1b3bffdf5ed4f3039ab5edd2f04/spec/schemas/_core.bulk.yaml#L56
What is the expected behavior?
should use more accurate definition for numeric types. https://swagger.io/docs/specification/v3_0/data-models/data-types/