phpdoc-parser icon indicating copy to clipboard operation
phpdoc-parser copied to clipboard

Documentation parser powering developer.wordpress.org

Results 61 phpdoc-parser issues
Sort by recently updated
recently updated
newest added

Right now the parser has very large memory requirements. I had to up my local install's available memory to run the parsing for core. 2GB on the VM and 1GB...

enhancement

Per 387fe21f1d20b6d1c4bf2f75a508bca4affddc62, we should do safer handling of uninstall. Just posting this here so there is an issue for it instead of only a TODO.

enhancement

Some of the parameter docs use lists. Markdown needs to be parsed in parameter docs. See this for reference: https://meta.trac.wordpress.org/ticket/197

enhancement
DevHub

http://txfx.net/wordpress-plugins/periods-in-titles/ allows periods in post and term slugs. I use it at, for example, http://genesischangelog.com/2.0.2 . It would be good if periods would be allowed for the `@since` taxonomy terms,...

wontfix

We are working on this from the contributor day of WordCamp Switzerland 2014 today. **Meta information** The basic idea is to improve the data presentation in the backend to show...

enhancement

Per now the devhub doesn't play well with deprecated parameters for function calls, an example of this would be the `get_the_author` function which used to have a parameter. The parser...

bug
enhancement

I've been thinking about the problem of requiring people to build templates to display the data that this importer generates. Right now, it's not ideal: - You have to register...

Someday Maybe

Do you have plans to map `require()`-s as in PHP XREF? http://wordpress.online1.hu/wp-load.php.xref.html

enhancement

Would be nice to make some links to either phpxref or the source in trac so you can see these functions in context.

enhancement