Skip to content

Conversation

@Raghunath-S-S-J
Copy link
Contributor

No description provided.

@Raghunath-S-S-J Raghunath-S-S-J changed the title Feature/sdk automation Automating SDK generation process Feb 4, 2025
],
"require": {
"php": ">=5.6",
"php": ">=8.1",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is quite the jump and with Xero updating API responses server side that are validated against an hardcoded list client side (the last one being the identifier of the subscription plans) please consider keeping this range very wide. Or remove the hardcoded validations to avoid breaking existing installs on sites that haven't yet been able to run on later versions of php.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would suggest bumping to support php version 7.1 as a minimum as that will allow you to use nullable parameters which you will need to get past errors like

Deprecated: XeroAPI\XeroPHP\Models\Accounting\Item::__construct(): Implicitly marking parameter $data as nullable is deprecated, the explicit nullable type must be used instead in /var/www/vendor/xeroapi/xero-php-oauth2/lib/Models/Accounting/Item.php:254.

on php 8.4 - see
https://wiki.php.net/rfc/deprecate-implicitly-nullable-types

and

https://www.php.net/manual/en/migration71.new-features.php

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

Successfully merging this pull request may close these issues.

5 participants