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
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.
And the returned api data is formatted with a decimal place: "effectiveLifeYears": 5.00,
"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.
The text was updated successfully, but these errors were encountered:
PETOSS-373
Sorry, something went wrong.
Thanks for raising an issue, a ticket has been created to track your request
No branches or pull requests
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.
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.
The text was updated successfully, but these errors were encountered: