Skip to content

Conversation

@melroy89
Copy link
Contributor

@melroy89 melroy89 commented Dec 8, 2025

?$var = null should not be used anymore, and will show deprecation warnings.

See: https://php.watch/versions/8.4/implicitly-marking-parameter-type-nullable-deprecated

Fixes: #69

@mgruner mgruner merged commit 18c4d69 into zammad:master Dec 8, 2025
8 checks passed
@melroy89 melroy89 deleted the patch-3 branch December 8, 2025 13:49
@mrohnstock
Copy link

mrohnstock commented Dec 19, 2025

hm, am I mistaken, or is it precisely your change that is causing the warning you want to fix - again, before your commit this issue was gone?

Since version 8.2, PHP requires nullable to be specified as a type, so ?HTTPClientInterface $client = null was correct.

@melroy89
Copy link
Contributor Author

hm, am I mistaken, or is it precisely your change that is causing the warning you want to fix - again, before your commit this issue was gone?

Since version 8.2, PHP requires nullable to be specified as a type, so ?HTTPClientInterface $client = null was correct.

Well apparently not anymore now with php 8.5, since it's deprecated in 8.4.

@melroy89
Copy link
Contributor Author

Or.. Homelab wait I'm very confused now. Should we revert this commit.?

@mrohnstock
Copy link

I think so, yes, you do revert the fix from #66 :/

melroy89 added a commit to melroy89/zammad-api-client-php that referenced this pull request Dec 20, 2025
mgruner pushed a commit that referenced this pull request Dec 23, 2025
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.

Depreciation: Implicitly nullable parameter declarations

3 participants