Repository navigation
[DEPRECATION] Param tags without name #362
Description
@param tag should always have a variable name in it's body, support for params without variable names will be dropped.
Supported formats will be: (option 3 does not really make any sense, but will be covered)
@param $var your description here
@param MyType $var your description
@param $var
@param MyType $var
Unsupported after this deprecation has been removed:
@param MyType your description here
@param MyType
Activity
williamdes commentedon Apr 6, 2024
And reported as invalid items I guess ?
jaapio commentedon Apr 8, 2024
Yes these will be reported as
InvalidTagnorkunas commentedon Apr 12, 2024
so basically this is opposite to symfony/symfony#54523 ?
williamdes commentedon Apr 12, 2024
the linked PR feels wrong, the types should always be present
If the param do not document anything (type hints exist), drop them
But if they do have a description, keep them in sync with native hints
Anyway, that's only my point of view 😁
jaapio commentedon Apr 12, 2024
Types are optional. I just noticed that the description of this issue is wrong. Thanks for the headsup @norkunas
kkmuffme commentedon Dec 7, 2025
@PARAM without a variable is extremely common for documentation of actions/filters in the WP ecosystem and found not only in WP itself but probably most plugins