Skip to content
docsv0.44.3

PluginRegistration

What `make` says about the one step it leaves to its caller: registering a new plugin. Six generators and the postcondition verifier each wrote this sentence, and every copy named the plugin by its fully qualified class name — «add App\Plugins\Blog\Blog::class to the list returned by config/plugins.php» (greenhouse evidence/1036, seq 88). But the house registers by the SHORT name: `plugins.register` takes `Blog` and resolves `src/Plugins/Blog/Blog.php`, and config/plugins.php lists `Blog::class` under a `use`. A guide that dictates the long form teaches the model a name the house never asks for (greenhouse decisions/0514). One owner, so the copies cannot drift again.

PluginRegistration::guidance()

public static function guidance(string $plugin): string

The guidance for a plugin `make` just created: register it by its short name.

Parameters

Parameters of guidance()
NameTypeDescription
$pluginstringthe plugin's short class name, e.g. `Blog`

PluginRegistration::notListed()

public static function notListed(string $plugin): string

The postcondition's advice when the plugin is not listed yet — same step, same short name.

Parameters

Parameters of notListed()
NameTypeDescription
$pluginstringthe plugin's short class name, e.g. `Blog`