id summary reporter owner description type status priority milestone component version severity resolution keywords cc focuses 24202 Self-explanatory argument values for new media functions SergeyBiryukov nacin "We've introduced a bunch of functions, some with a relatively long list of arguments, which accept booleans: {{{ function get_content_media( $type, &$content, $html = true, $remove = false, $limit = 0 ) function get_embedded_media( $type, &$content, $remove = false, $limit = 0 ) function get_content_audio( &$content, $html = true, $remove = false ) function get_embedded_audio( &$content, $remove = false ) function get_content_video( &$content, $html = true, $remove = false ) function get_embedded_video( &$content, $remove = false ) function get_content_images( &$content, $html = true, $remove = false, $limit = 0 ) function get_content_image( &$content, $html = true, $remove = false ) function get_content_galleries( &$content, $html = true, $remove = false, $limit = 0 ) function get_post_galleries( $post_id = 0, $html = true ) function get_post_gallery( $post_id = 0, $html = true ) function get_content_chat( &$content, $remove = false ) function get_content_quote( &$content, $remove = false, $replace = '' ) function get_content_url( &$content, $remove = false ) }}} I wonder if we can convert them to use arrays instead for future-proof changes, or at least switch from booleans to self-explanatory values, per our [http://make.wordpress.org/core/handbook/coding-standards/php/#self-explanatory-flag-values-for-function-arguments coding standards]. Otherwise, we might fall into a trap of `submit_button()`: #20492. " enhancement closed high 3.6 Media 3.6 major fixed dev-feedback has-patch