XeroAPI/Xero-OpenAPI

Asset Type definition inconsistent with Xero interface

winterlimelight opened this issue · 2 comments

winterlimelight commented

In the file https://github.com/XeroAPI/Xero-OpenAPI/blob/master/xero_assets.yaml the field effectiveLifeYears is defined as type: integer

However in the Xero interface it is a decimal, and seems now to force the value to have decimal places.
image

And the returned api data is formatted with a decimal place:
"effectiveLifeYears": 5.00,

Because my generated code uses integer as the type definition, it fails when trying to parse this field.

I therefore believe this should be type: number rather than integer.

github-actions commented

PETOSS-373

github-actions commented

Thanks for raising an issue, a ticket has been created to track your request