add_theme_support() docs do not mention second parameter $arguments

[kevinwhoffman]

add_theme_support() has two parameters, $feature and $arguments as documented in the Codex:

​https://codex.wordpress.org/Function_Reference/add_theme_support

<?php add_theme_support( $feature, $arguments ); ?>

The Code Reference only lists one parameter, $feature:

​https://developer.wordpress.org/reference/functions/add_theme_support/

The Code Reference should be updated to document the $arguments parameter for use cases like the following:

<?php add_theme_support( 'post-thumbnails', array( 'post_type' ) ); ?>

Moved from ​#meta1764

[DrewAPicture]

In 37671:

Docs: Improve documentation for the $feature parameter in the DocBlock for add_theme_support().

See #32246. See #37067.

[DrewAPicture]

In 37672:

Docs: Add documentation for the variadic second parameter, $args, accepted by add_theme_support().

h/t kevinwhoffman
Fixes #37067.

[DrewAPicture]

Due to the extensive context of the second parameter, $args, let's handle migrating that content from the Codex into the "More Information" section instead of trying to squeeze it into the DocBlock.

[DrewAPicture]

@kevinwhoffman I've migrated the Codex information to the Code Reference page. The new argument docs will come over when we reparse following the 4.6 release.

​https://developer.wordpress.org/reference/functions/add_theme_support/

[kevinwhoffman]

Replying to DrewAPicture:

@kevinwhoffman I've migrated the Codex information to the Code Reference page. The new argument docs will come over when we reparse following the 4.6 release.

Note that => in all of the array examples is showing as =>

Other than that, the page is so much more helpful now. Thanks.

[DrewAPicture]

Replying to kevinwhoffman:

Replying to DrewAPicture:

@kevinwhoffman I've migrated the Codex information to the Code Reference page. The new argument docs will come over when we reparse following the 4.6 release.

Note that => in all of the array examples is showing as =>

Yeah, that's an encoding problem we need to fix on DevHub. /cc @coffee2code

[coffee2code]

@DrewAPicture: For the 'more info' for this post, the multiple > were there in the raw content. I simply edited the post to change > to > and all appears well.

[kevinwhoffman]

Replying to coffee2code:

@DrewAPicture: For the 'more info' for this post, the multiple > were there in the raw content. I simply edited the post to change > to > and all appears well.

There's an extra ; on line 8 of the custom-header example.

[coffee2code]

@kevinwhoffman: Thanks! Fixed.