WordPress / WordPress/phpdoc-parser
`@param` tags with `&` in varaible names are not parsed as parameters
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 239
- Forks
- 81
- Avg merge
- 16h 29m
- Merged PRs (30d)
- 8
Description
I originally reported it in WordPress core trac 35974
Below is the summary of the issue.
While documenting hooks, if & is added in the @param tag, then they are not regonized as parameters in the developer docs.
Eg: Look under parameter sub-heading in the following pages
https://developer.wordpress.org/reference/hooks/http_api_curl/
https://developer.wordpress.org/reference/hooks/posts_where/and about a dozen pages where the parameters are not documented properly.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the @param examples containing 6 and compare the parameter sections on the linked developer.wordpress.org hook pages. Trace how phpdoc-parser recognizes parameter names, then verify that names containing 6 are included in the generated documentation for the affected hooks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100