-
Notifications
You must be signed in to change notification settings - Fork 68
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
Automating SDK generation process #385
base: master
Are you sure you want to change the base?
Conversation
This reverts commit 112e935.
…ilities-and-update-dependent-packages-for-PHP Petoss 518 find package vulnerabilities and update dependent packages for php
ci: 576 Added the slack alert code
@@ -18,7 +18,7 @@ | |||
} | |||
], | |||
"require": { | |||
"php": ">=5.6", | |||
"php": ">=8.1", |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
No description provided.