Tracking issue: Improve types for certain functions

[swissspidy]

I was just experimenting with migrating a project from PHPStan level 9 to 10, and found a lot of instances of mixed types. I thought I'd open a tracking issue to figure out if and how those could be improved, either in phpstan-wordpress or (preferably) wordpress-stubs:

• get_registered_settings(): document the shape of the returned settings (see register_setting())
• WP_Taxonomy::$labels: define object shape with expected keys (see get_taxonomy_labels())
• WP_Post_Type::$labels: define object shape with expected keys (see get_post_type_labels())
• WP_Taxonomy::$cap: define object shape with expected keys
• WP_Post_Type::$cap: define object shape with expected keys (see get_post_type_capabilities())
• WP_User::$caps: define as array<string, bool>
• wp_parse_args(): could an extension be built to dynamically set the return type based on the shape of the arguments?

[IanDelMar]

• WP_User::$caps: define as array<string, bool>

Couldn’t this be implemented directly in core? Core already uses the array<keyType, valueType> notation in some places. I also don’t see anything in the coding standards that leads me to believe array<keyType, valueType> is not permitted.

[swissspidy]

Yeah maybe. But also in the stubs repo it could be enhanced to use generics perhaps