Minn\Extension

What a Minn extension is: a class the engine constructs once per request and asks to register what it provides. Everything it can touch is on the Seams object; there is no global state to reach for.

Where the engine looks for the seams an extension registered. The request's runtime holds them, so nothing here keeps state of its own and a request cannot inherit the extensions of the one before it. Before the front has loaded any (REST and the command line never do) there are none.

Finds extensions under wp-content/plugins and wp-content/mu-plugins, decides which are active, autoloads them, and asks each to register. An extension that throws is logged and skipped; the page still renders.

minn.json, read as data. A folder under wp-content/plugins (or mu-plugins) with this file is an extension; the same folder may also be a WordPress plugin, in which case the two share a name and a version.

{ "name": "Block Visibility for Minn", "version": "1.0.0", "license": "MIT", "replaces": ["block-visibility/block-visibility.php"], "autoload": {"Minn\\Ext\\BlockVisibility\\": "src/"}, "extension": "Minn\\Ext\\BlockVisibility\\Extension", "shortcodes": ["example_tag"], "blocks": ["vendor/block"], "types": [{"slug": "zz_note", "name": "Notes", "rest_base": "zz-note"}], "needs": {"http": ["https://api.example.com/"]} }

"replaces" names the WordPress plugin files whose behaviour this extension stands in for; the extension is active whenever one of them is in active_plugins, or when its own folder is listed there, or when it is named in the minn_active_extensions option. "shortcodes" and "blocks" are the content tokens preflight treats as provided instead of missing. "types" are extra post types the engine should serve on wp/v2. "needs" says what the extension reaches outside the process: "http" is the URL prefixes its $minn->http may request (true for any public host).

Everything the extensions registered for this request, handed from Seams to the runner once.

The engine's side of the seams: what the loader collected, called at the right moment and in registration order. An extension never sees this class; it sees Seams, which is only the eight registrations.

Where an extension can take part in a request: eight typed registrations, the request they run in, and the outgoing HTTP its minn.json asks for. This is the whole surface an extension sees. Each extension registers on its own (forExtension), and what it registered joins the request's once its register() returns (adopt). The engine calls what was registered through SeamRunner, at the right moment and in registration order.

The shortcode syntax in rendered content: [tag], [tag attr="v" flag], [tag]inner[/tag], and [[tag]] as the escaped literal. Unregistered tags stay as written, which is what the reference shows for a plugin that is not installed.