Detailed thinkPHP5.0 framework module design

This article mainly introduces the thinkPHP5.0 frameworkmodule design, and briefly describes the thinkPHP5.0directory structure, naming standards and analysis in the form of examples The principles and access methods of the module Class Library are explained. Friends in need can refer to

. This article describes the thinkPHP5.0 framework module design with examples. Share it with everyone for your reference, the details are as follows:

The 5.0 version has a flexible design for the function of the module. It adopts a multi-module architecture by default and supports a single module design. The namespace## of all modules is #Both use app as the root namespace (can be configured to change).

Directory structure

The standard application and module directory structure is as follows:

Follow the naming convention of ThinkPHP5.0, and the module directories all use lowercase and Underline naming.

Please avoid using PHP reserved keywords in the module name (see http://php.net/manual/zh/reserved.keywords.php for the list of reserved words), otherwise it will cause system errors. .

The common module is a special module that prohibits direct access by default. It is generally used to place some public class libraries for

inheritance of other modules.

Module Class Library

The namespace of the class library file under a module uniformly starts with app\module name, for example:

where app It can be changed by definition. For example, we modify it in the application configuration file:

Then, the class library namespace of the index module becomes:

More about class libraries and For the relationship between namespaces, please refer to the next previous article "Detailed Explanation of ThinkPHP5.0 Framework Namespaces".

Module and controller hiding

Since the default is to use multi-module support, the current module must be identified in the URL address in the case of multiple modules. If there are only For a module, you can bind the module by adding the following code to the public file of the application:

After binding, our URL access address becomes:

The module is the index module.

If your application is relatively simple and has only one module and controller, you can bind the module and controller in the application public file, as follows:

After setting, Our URL access address becomes:

The module accessed is the index module, and the controller is the Index controller.

Single module

If your application is relatively simple and has only one module, it can be further simplified to use a single module structure as follows:

First define it in the application configuration file:

Then, adjust the structure of the application directory as follows:

URL access address becomes

At the same time, The namespace of the application class library under the single module design has also been adjusted, for example:

The original

becomes

More URL simplification and Customization is also possible through the URL routing feature.

The above is the detailed content of Detailed thinkPHP5.0 framework module design. For more information, please follow other related articles on the PHP Chinese website!