Download the PHP package olekhy/view-model-service without Composer
On this page you can find all versions of the php package olekhy/view-model-service. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download olekhy/view-model-service
More information about olekhy/view-model-service
Files in olekhy/view-model-service
Package view-model-service
Short Description Helper for view modeling
License MIT
Homepage https://github.com/olekhy/view-model-service
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package view-model-service
View Model service
The module named "ViewModelService" could be used for:
- Inserting data obtained from database or user's input in the instance of the View Model via appropriate mapper.
- Latter inserting (applying) data to the View Model and building an instance at the time when View Model was called in template.
- Convenience at coding in IDE from the autocomplete for the View Models in the view template.
- Flexible and secure approach of the logic how data will be mapped to the View Model (Using of mappers).
- Lazy loading data in view model via Repository without using of controller.
Explaining of the process and root idea
Firstly we will have in codebase of project many View Models classes which oneself a simples presentation of variables that we obtained from database or another sources and will be using in our view templates. All of the View Model classes needed to be named by convention ConcreteNameViewModel and must implement an interface ViewModelInterface.
Parallel to the view models we create View Model Mapper classes, the purpose of the mapper class is the mapping data to the View Model instance. Naming convention for the Mapper class is similar to the View Model naming and and looks like this ConcreteNameViewMapper. All mappers implement an interface ViewMapperInterface and must realizing the map() method which contains logic that describes how will be mapped data to the View Model.
Process of applying of data is internally segregated into two logical independent processes, first is the recording in the repository a recipe which describes how can the View Model created and second is creation of a real View Model instance. The purpose of this segregation is performance of execution of the request as simple as we can say the View Model Instance will be created only at calling also on requirement in the template.
Next we explain how we could work with the View Model Service
As for example we are at Request in UserController::actionShowProfile()
now in View Template
Important is that the both UserProfileViewModel and UserProfileViewMapper classes exists in the code scope.
Follow you can see some other usage cases:
