FunctionDeclarations/RemovedImplicitlyNullableParam: bug fix x 2 (uppercase null/mixed & FQN null) by jrfnl · Pull Request #1897 · PHPCompatibility/PHPCompatibility
added 2 commits
September 1, 2025 21:47
…for uppercase `null`/`mixed` in type declaration Includes tests via updating some pre-existing tests.
…for FQN `null` in default value Not commonly used, but it is valid PHP. Note: FQN `null` in a type declaration is not allowed and therefor not accounted for. Includes tests.
wimg approved these changes Sep 5, 2025
wimg
deleted the
feature/removedimplicitlynullable-allow-fqn-and-uppercase-null-mixed
branch
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