Merged
Conversation
Contributor
Author
|
@TavoNiievez Do you have any objections against merging this PR and #19 and tag a new release afterwards? |
Member
Contributor
Author
@TavoNiievez Done. Both PRs make sense to me. |
TavoNiievez
approved these changes
Apr 2, 2025
Contributor
Author
|
@TavoNiievez Can we have a new release of this package even if #18 is not ready? That would be great because we could get rid of the PHP 8.4 deprecation warnings. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
#19 fixes the remaining PHP 8.4 deprecation warnings