fix: better management of numbers in OpenApi3Generator

[jgazeau]

Hello,
I found an issue with defaultValue management when generating the OpenApi.

When generating the resource snippet from Spring restdocs they can look like that:

"requestParameters" : [ {
      "name" : "one",
      "attributes" : { },
      "description" : "BigDecimal query param",
      "ignored" : false,
      "type" : "NUMBER",
      "optional" : false,
      "default" : 1
    }

When using ePages to generate the associated API, the NUMBER with value 1 is interprated as an Integer and casting it as a BigDecimal will fail. (e.g. class java.math.Integer cannot be cast to class java.math.BigDecimal)

Because a BigDecimal has no string representation, and parsing the resource.json from spring restdocs to the ePages ResourceModel has an Any type for the defaultValue, numbers should be transformed to BigDecimal but not casted.

I've created this PR to solve it, as well as enhancing tests to check all possible cases.
(For the OpenAPIv2 no changes to be done as default value is not managed)

Kr,

Jordan.

[coveralls]

Coverage increased (+0.02%) to 93.024% when pulling 304219d on jgazeau:fix/openapi3generator_numbers into 02c7a41 on ePages-de:master.

[jgazeau]

Hello @ooz ,

I didn't created an issue related to this so don't hesitate to tell me if I need to do so.
Also do you know if it is possible to check this MR and create a release afterwards when you have time ?
Kr,

Jordan.

[tadlakha9]

commenting for notifications

[stour]

@ooz I'm also very interested in this fix, any idea when you'll have the opportunity to take it into account ?

[ooz]

Sorry for the delay, I've been on extended leave.

But next week is a hackathon at ePages, in which scope I'm going to take care of this project more, open PRs and sort the issues.

[tadlakha9]

Hello @ooz can we also create the tag to get the benefit of these changes