e.g.

* @param array<string, array{name: string, class: string, placeholder?: string, type: string, label: string, required: bool}> $form_fields array of form fields and attributes
* @param array<string, string>|false                                                                                          $saved_form saved form values

isn't parsed correctly and ends up completely garbled in the .json

@johnbillion

I'm including this library in my plugin via composer and then tried executing "php ./vendor/bin/wp-hooks-generator " from plugin's root folder in the command line (Ubuntu server) but got the following error:

`dir=$(cd "${0%[/\]*}" > /dev/null; cd ../johnbillion/wp-hooks-generator/bin && pwd)

if [ -d /proc/cygdrive ]; then case $(which php) in $(readlink -n /proc/cygdrive)/*) # We are in Cygwin using Windows php, so the path must be translated dir=$(cygpath -m "$dir"); ;; esac fi

"${dir}/wp-hooks-generator" "$@"`

Any idea what went wrong? ...or further examples on how to use this library properly?

My intention is to use the generator to list all hooks from all the WordPress plugins installed. So, gussing I should put the plugins root folder in the --src= parameter, but can not proceed to that step just yet.

Thanks!

As now install this create conflicts with Psalm as example because of php-parser package.

Maybe they are old (2 years~) in the composer.json and just need a bump.

Parse Error: Syntax error, unexpected '?', expecting T_VARIABLE on line 14Parse Error: Syntax error, unexpected '?', expecting T_VARIABLE on line 138Parse Error: Syntax error, unexpected '?', expecting T_VARIABLE on line 14Done

No idea in which files the tool encountered a parse error. Would it be possible to include the file name in the error message?

would be nice if filters/action that are called with do_action_deprecated or apply_filters_deprecated had a field deprecated: true or something

Or action_deprecated/filter_deprecated type would maybe even make more sense

Happy to provide a PR

Parse Error: Syntax error, unexpected ')' on line ...

when doing this:

/**
 * Get packages details
 *
 * @param array
 * @param int $order_id
 */
$hello = apply_filters(
	'hello_world',
	array(),
	$order_id,
);

Bumps minimist from 1.2.0 to 1.2.5.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Fixes https://github.com/johnbillion/wp-hooks/issues/6.

Unfortunately a specific PHPDoc tag never got implemented to document the common values for dynamic hook names, but we have now got a mostly standardised use of "Possible hook names include:" followed by an unordered list (example: https://developer.wordpress.org/reference/hooks/type_template_hierarchy/), so we can parse that list if it exists and store the result in a new property.

I've hooked up the resulting aliases to the autocomplete and hover provision in WordPress Hooks Intellisense for VS Code:

Reflector gives an error "The given file should be a string, should exist on the filesystem and should be readable" if the file is not readable.

This seems to be an issue with what is going on in the background with the old version of reflector used here, as I did not encounter this issue with other libraries or the latest version of reflector when I run (e.g. psalm) on same files. This just snoozes the error.

I have the following function that fails parsing because of the () call at the end:

$container = $container ?: ( function() {
	// logic here
} )();

IIFE are supported as of PHP 7.0 and up.

Closes https://github.com/johnbillion/wp-hooks-generator/issues/9

The "docs" are always empty, since a) nobody ever documents these and b) if someone really wants to document, we can still add that later.

Used the original nodes for all things (instead of the WP Reflector nodes), as this code is/will be used in other repos that only use the phpDocumentor/Reflector directly (and I need args from the reflector node anyway, so it's easier to maintain, as it's the widely used reflector syntax instead of the WP mumbo jumbo)

https://developer.wordpress.org/reference/functions/wp_schedule_single_event/ https://developer.wordpress.org/reference/functions/wp_schedule_event/

Both can declare hooks that will be called. These should be included in actions.json ?

The WP Parser library converts long descriptions for hooks into HTML from their source markdown. A consumer may want the raw markdown so it can convert it itself instead of having to deal with HTML.