je-query-builder-custom-type

What problem does it solve?

This Skill solves the problem of extending JetEngine Query Builder with new query data sources when the built-in types are insufficient, so listings, widgets, and REST/API usage can rely on a properly registered, reusable query type.

Core Features & Use Cases

• Registers runtime query type via the factory hook: extend \Jet_Engine\Query_Builder\Queries\Base_Query and register it on jet-engine/query-builder/queries/register so the Query Builder can execute your data source.
• Registers editor UI via the editor hook: extend \Jet_Engine\Query_Builder\Query_Editor\Base_Query and register it on jet-engine/query-builder/query-editor/register so admins can configure the query type in the UI.
• Implements the required pagination and caching contract: provide _get_items(), get_items_total_count(), get_items_page_count(), get_items_pages_count(), and get_current_items_page(), using Base_Query caching methods when needed.
• Supports modern integration surfaces: ensures participation in JE 3.8+ MCP tool exposure and the frontend query inspector by following the Base_Query expectations.
• Use cases: HPOS WooCommerce orders, custom DB tables, third-party REST sources, or computed datasets used by JetEngine listings, dynamic widgets, or REST API endpoints.

Quick Start

Implement a new runtime query class extending \Jet_Engine\Query_Builder\Queries\Base_Query and a matching editor class extending \Jet_Engine\Query_Builder\Query_Editor\Base_Query, then register both together on the paired JetEngine hooks using the same slug.