Prevent deprecation errors in PHP 8.4 #13
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Bump package version
|
any updates on this? We're currently running php 8.x override patches |
|
I submitted a support ticket and got a generic response. I also made a post in r/MailChimp on Reddit, which they seem to participate in actively. Hopefully, this will get merged soon. |
|
@lvanstrijland and you clean their sdk too |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I created this PR to make sure we prevent deprecation warning for PHP 8.4 because of the explicit nullable type.
Kind Regards,
Laurens van Strijland
Note: This repository is auto-generated, and does not accept pull requests.
To make changes or open issues for this SDK, use the code generation repository.