registerExtension()#
Register a HydePHP extension within the HydeKernel.
Typically, you would call this method in the register method of a service provider. If your package uses the standard Laravel (Composer) package discovery feature, the extension will automatically be enabled when the package is installed.
Hyde::registerExtension(class-string<\Hyde\Foundation\Concerns\HydeExtension> $extension): void
getExtension()#
Get the singleton instance of the specified extension.
Hyde::getExtension(class-string<T> $extension): T
hasExtension()#
Determine if the specified extension is registered.
Hyde::hasExtension(class-string<\Hyde\Foundation\Concerns\HydeExtension> $extension): bool
getExtensions()#
No description provided.
Hyde::getExtensions(): array<\Hyde\Foundation\Concerns\HydeExtension>
getRegisteredExtensions()#
No description provided.
Hyde::getRegisteredExtensions(): array<class-string<\Hyde\Foundation\Concerns\HydeExtension>>
getRegisteredPageClasses()#
No description provided.
Hyde::getRegisteredPageClasses(): array<class-string<\Hyde\Pages\Concerns\HydePage>>
replacePageClass()#
Replace a registered page class with an application subclass.
Register replacements in a service provider's register method before the Hyde Kernel boots. Changing filesystem or routing behavior on the replacement is not supported.
Hyde::replacePageClass(class-string<HydePage> $original, class-string<HydePage> $replacement): void
- Throws: \BadMethodCallException If Kernel booting has already started
- Throws: \InvalidArgumentException If the classes are incompatible or the replacement conflicts with an existing mapping
resolvePageClass()#
Resolve a page class to its registered replacement, if any.
Custom extension discovery handlers should resolve page classes before assigning them to source files or constructing pages so application replacements are honored.
Hyde::resolvePageClass(class-string<HydePage> $pageClass): class-string<HydePage>