WP_View_Config_Data::apply_filters( string $kind, string $name ): array

135	public function apply_filters( $kind, $name ) {136		/**137		 * Filters the view configuration for a given entity.138		 *139		 * The dynamic portions of the hook name, `$kind` and `$name`, refer to the140		 * entity kind (e.g. `postType`) and the entity name (e.g. `page`),141		 * lowercased — so the `postType`/`page` entity maps to the142		 * `get_entity_view_config_posttype_page` hook.143		 *144		 * Callbacks receive a WP_View_Config_Data object and change the145		 * configuration through its methods. Each write method takes the schema146		 * version the change was authored against as its second argument,147		 * and returns the object for chaining:148		 *149		 * - `merge( $patch, $version )` merges a partial change into the current150		 *   configuration. It touches only the top-level keys the patch names, and151		 *   merges each named value into the current one by shape: a scalar152		 *   replaces, an associative array merges key by key, and a list merges by153		 *   member identity (`id`, `slug`, or `field`). A `null` value drops the154		 *   key it names, resetting it to its default.155		 * - `replace( $patch, $version )` applies a patch exactly like `merge()`,156		 *   but swaps any list it names wholesale instead of merging that list by157		 *   member identity.158		 * - `set( $patch, $version )` also touches only the keys the patch names,159		 *   but swaps each named value in wholesale, dropping whatever the key held160		 *   before — for a callback that owns those keys outright.161		 * - `remove( $spec, $version )` deletes named properties. The spec mirrors162		 *   the configuration shape: a list of names deletes entries at that level,163		 *   and a nested map recurses to prune from within a named value, down to164		 *   individual list members.165		 *166		 * A change that declares an unsupported schema version is rejected and does167		 * not alter anything. As with any filter, each callback's return value is168		 * passed to the next callback as `$data`, so callbacks must return the169		 * container they received: a callback that returns nothing, or any other170		 * value, hands that result to every callback hooked at a later priority171		 * instead of the container. Since the write methods return the container,172		 * a callback can end with `return $data->merge( $patch, $version );`.173		 *174		 * @since 7.1.0175		 *176		 * @param WP_View_Config_Data $data   The view configuration container177		 *                                    for the entity, exposing the178		 *                                    `default_view`, `default_layouts`,179		 *                                    `view_list`, and `form` keys.180		 * @param array               $entity {181		 *     The entity the configuration is built for.182		 *183		 *     @type string $kind The entity kind.184		 *     @type string $name The entity name.185		 * }186		 */187		apply_filters(188			wp_get_entity_view_config_hook_name( $kind, $name ),189			$this,190			array(191				'kind' => $kind,192				'name' => $name,193			)194		);195 196		// Discard any keys the filter introduced that are not part of the197		// documented configuration shape.198		return array_intersect_key( $this->get_data(), array_flip( self::CONFIG_KEYS ) );199	}