Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expand docs for plugin events #7928

Merged
merged 1 commit into from
Oct 15, 2024
Merged

Expand docs for plugin events #7928

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions en/plugins.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,14 +107,17 @@ Plugins offer several hooks that allow a plugin to inject itself into the
appropriate parts of your application. The hooks are:

* ``bootstrap`` Used to load plugin default configuration files, define
constants and other global functions.
constants and other global functions. The ``bootstrap`` method is passed the
current ``Application`` instance giving you broad access to the DI container
and configuration.
* ``routes`` Used to load routes for a plugin. Fired after application routes
are loaded.
* ``middleware`` Used to add plugin middleware to an application's middleware
queue.
* ``console`` Used to add console commands to an application's command
collection.
* ``services`` Used to register application container services
* ``services`` Used to register application container service. This is a good
opportunity to setup additional objects that need acccess to the container.

By default all plugins hooks are enabled. You can disable hooks by using the
related options of the ``plugin load`` command:
Expand Down