Update Error Docs - #15427

The latest errorsIdentifiers.json update only moved the phpunit.assertEmpty source line (L48 → L54). That move comes from phpstan-phpunit making AssertEmptyIsDiscouragedRule auto-fixable. Seven identifiers for the new @pure-unless-parameter-passed PHPDoc tag (phpstan-src 2.3.x) were also still undocumented.

New pages

• pureFunction.nonOptionalParameterPassed, pureMethod.nonOptionalParameterPassed, purePropertyHook.nonOptionalParameterPassed: the tag names a parameter that is not optional, so the function is never pure.
• pureFunction.parameterPassedNotByRef, pureMethod.parameterPassedNotByRef, purePropertyHook.parameterPassedNotByRef: the tag names a by-value parameter, so passing it cannot add a side effect.
• method.impureOverridePureUnlessParameterPassed: an @phpstan-impure method overrides a parent method marked @pure-unless-parameter-passed (bleeding edge, reportMethodPurityOverride).

The research covered FunctionPurityCheck, MethodSignatureRule and their test fixtures. The function, method and override examples, and the suggested fixes, were checked on the playground, and each example reports the expected identifier.

Note on purePropertyHook.*: I couldn't reproduce these two identifiers. MutatingScope::enterPropertyHook() passes empty pure-unless parameter lists to the hook reflection, so the tag is never read on hooks right now. The identifiers exist only because the rule builds them with sprintf. The existing purePropertyHook.redundantUnlessCallable page has the same limitation. These pages explain why the tag can't work on a set hook, whose $value is always required and passed by value, and suggest removing it.

Updated page

• phpunit.assertEmpty: says the call can be rewritten with --fix and lists the replacements by native type: bool → assertTrue/assertFalse, array → assertCount(0)/assertNotCount(0), int → assertSame(0)/assertNotSame(0), and a nullable final class that isn't Countable → assertNull/assertNotNull.

🤖 Generated with Claude Code