Minn\Objects

A registered block type as the WordPress layer hands it to plugins (WP_Block_Type): its attributes, supports, styles and render callback. The engine knows these objects by this mark and finds them through Runtime\Handoff, so it never names the WordPress layer's class.

A comment as the WordPress layer hands it to plugins (WP_Comment). The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

A comments query as the WordPress layer hands it to plugins (WP_Comment_Query). The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

A registered script or style as the WordPress layer hands it to plugins (_WP_Dependency): its handle, source, dependencies, version and extra data. The engine knows these objects by this mark, so it never names the WordPress layer's class.

The request's environment as the WordPress layer hands it to plugins (WP, the $wp global): the query variables parsed from the request and the headers sent. The engine knows it by this mark, so it never names the WordPress layer's class.

A list of errors as the WordPress layer hands it to plugins (WP_Error): codes with their messages and data. The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

An HTTP response as the WordPress layer hands it to plugins (WP_HTTP_Response): its data, status and headers. The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

A post as the WordPress layer hands it to plugins (WP_Post). The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

A registered post type as the WordPress layer hands it to plugins (WP_Post_Type): its labels, capabilities and settings. The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

A posts query as the WordPress layer hands it to plugins (WP_Query): its variables, flags, posts and loop. The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

A block being rendered as the WordPress layer hands it to plugins (WP_Block): its parsed block, attributes, context and inner blocks. The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

A REST request as the WordPress layer hands it to plugins (WP_REST_Request): its route, method, parameters, headers and body. The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

A REST response as the WordPress layer hands it to plugins (WP_REST_Response): its data, status, headers and links. The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

The REST server as the WordPress layer hands it to plugins (WP_REST_Server). The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

The rewrite object as the WordPress layer hands it to plugins (WP_Rewrite): the permalink structures, the extra rules and endpoints plugins add, and the rules built from them. The engine knows it by this mark, so it never names the WordPress layer's class.

A user's sessions as the WordPress layer hands them to plugins (WP_Session_Tokens, or the manager session_token_manager names): made, read, verified and ended. The engine knows them by this mark and asks for them through Runtime\Handoff, so it never names the WordPress layer's class.

The site's locale as the WordPress layer hands it to plugins (WP_Locale): the names of weekdays and months, the number format and the text direction. The engine knows it by this mark and makes it through Runtime\Handoff, so it never names the WordPress layer's class.

A sitemap provider as the WordPress layer hands it to plugins (WP_Sitemaps_Provider and its kinds): the object subtypes it lists and their URLs. The engine knows these objects by this mark, so it never names the WordPress layer's class.

The sitemaps as the WordPress layer hands them to plugins (WP_Sitemaps): the providers registered and the index and stylesheets they serve. The engine knows them by this mark, so it never names the WordPress layer's class.

A registered taxonomy as the WordPress layer hands it to plugins (WP_Taxonomy): its labels, capabilities and settings. The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

A term as the WordPress layer hands it to plugins (WP_Term). The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

A terms query as the WordPress layer hands it to plugins (WP_Term_Query). The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

A theme as the WordPress layer hands it to plugins (WP_Theme): its headers, folders, templates and files. The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

One origin's theme.json data as the WordPress layer hands it to the wp_theme_json_data_ filters (WP_Theme_JSON_Data), which may change it. The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

The toolbar as the WordPress layer hands it to plugins (WP_Admin_Bar): the nodes and groups a menu callback adds. The engine knows it by this mark, so it never names the WordPress layer's class.

An upgrader as the WordPress layer hands it to plugins (WP_Upgrader and the plugin and theme upgraders): it fetches, unpacks and installs a package. The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

What an upgrader reports through (WP_Upgrader_Skin and its kinds): the feedback and errors of an install or update. The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

A user as the WordPress layer hands it to plugins (WP_User). The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

A users query as the WordPress layer hands it to plugins (WP_User_Query). The engine knows these objects by this mark and makes them through Runtime\Handoff, so it never names the WordPress layer's class.

A widget as the WordPress layer hands it to plugins (WP_Widget): its id base, name, options and the form and update methods a widget class writes. The engine knows these objects by this mark, so it never names the WordPress layer's class.