Skip to content
This repository has been archived by the owner on Jan 29, 2020. It is now read-only.

Commit

Permalink
Documents ability to use any class name for modules
Browse files Browse the repository at this point in the history
  • Loading branch information
weierophinney committed Jul 11, 2017
1 parent f224c6c commit 4ee0580
Show file tree
Hide file tree
Showing 2 changed files with 11 additions and 0 deletions.
8 changes: 8 additions & 0 deletions doc/book/module-class.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,14 @@ As an example, provided the module name "MyModule",
(typically `Zend\Loader\ModuleAutoloader`) to find and include the
`MyModule\Module` class if it isn't already available.

> ### Module classes
>
> - Since 2.8.0
>
> Module classes can now be named anything, so long as they are autoloadable, and
> you use the fully qualified class name when registering it with the
> `ModuleManager`.
The directory structure of a module named "MyModule" might start out looking
something like this:

Expand Down
3 changes: 3 additions & 0 deletions doc/book/module-manager.md
Original file line number Diff line number Diff line change
Expand Up @@ -117,6 +117,9 @@ retrieve the module class from the `ServiceManager`.
This is the default module resolver. It attaches to the `loadModule.resolve`
event and returns an instance of `{moduleName}\Module`.

Since 2.8.0, if the module name provided resolves to a fully qualified class
name, it returns that verbatim.

### OnBootstrapListener

If a module class implements
Expand Down

0 comments on commit 4ee0580

Please sign in to comment.