DocblockTypeContradiction with get_settings_errors() about wordpress-stubs

[johnbillion]

You can add an entry to functionMap.php with the correction, but to be honest if I were you I would just place the correction in your application code. For example:

/**
 * @var array<int|string, array{
 *   setting: string,
 *   code: string,
 *   message: string,
 *   type: string,
 * }> $errors
 */
$errors = get_settings_errors( ... );

[mcaskill]

How would you introduce this change?

With psalm/psalm-plugin-wordpress, the solution so far has been add new type information to a stubs override file. I recently started tinkering with that file but there's issues with it.

You can add an entry to functionMap.php with the correction […]

Thanks for the information. I had not looked into the specific details of how this package builds the stubs.

[…] but to be honest if I were you I would just place the correction in your application code.

I agree. Especially, if the ticket might be merged in time for the next maintenance release of WordPress or a few years from now 😛

[mcaskill]

My ticket on the WordPress Trac has been merged, thanks to @johnbillion.

[szepeviktor]

Hello @mcaskill! 👋🏻
Thank you for your report.

Stubs are automatically generated.
There are two files in the root: generator and visitor.
How would you introduce this change?