Skip to content
New issue

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

Asset Type definition inconsistent with Xero interface #575

Open
winterlimelight opened this issue Dec 7, 2023 · 2 comments
Open

Asset Type definition inconsistent with Xero interface #575

winterlimelight opened this issue Dec 7, 2023 · 2 comments

Comments

@winterlimelight
Copy link

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.

Copy link

github-actions bot commented Dec 7, 2023

PETOSS-373

Copy link

github-actions bot commented Dec 7, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant