Closed IanSimpson closed 2 weeks ago
PETOSS-430
Thanks for raising an issue, a ticket has been created to track your request
I've checked the OpenAPI spec at https://github.com/XeroAPI/Xero-OpenAPI/blob/master/xero_accounting.yaml and these new types are not currently included, so I presume this is the first step?
I've submitted an issue there too https://github.com/XeroAPI/Xero-OpenAPI/issues/593
Incidentally, it also hasn't been updated in the documentation at https://developer.xero.com/documentation/api/accounting/types/#organisation, so I guess top marks for consistency if nothing else.
New release has resolved this.
This is a future bug - it's not a bug yet, but will become one on July 1 when IGNITE, GROW and COMPREHENSIVE organisation classes are launched.
Describe the bug The Organisation class (like all models) checks all ENUM values on initialization, and throws an exception if an unknown value is encountered.
Presently the valid classes are:
This excludes those three new classes. After July 1, loading any organisation of one of these new types will cause an exception, even if you're not looking at the class
To Reproduce Steps to reproduce the behavior:
Expected behavior That we can load things without exceptions.
Additional context I previously raised an issue (https://github.com/XeroAPI/xero-php-oauth2/issues/291) based around the exact same change 2 years ago. This was converted to a discussion (https://github.com/XeroAPI/xero-php-oauth2/discussions/309), and then has been ignored for 2 years.
At the time I noted this would happen again, and suggested a couple of possible workarounds:
Both suggestions have been ignored, and once more, I find myself in a situation where I have three weeks to update, test and deploy on several applications, but no SDK update available.
Please address this urgently so I can start the update process next week and don't risk failures for clients in July.
You also need to just do better with this - two years since my original comment and we're being stitched up again.