yireo / magento2-common-view-models
yireo/magento2-common-view-models
Common ViewModels for usage in Magento 2
Gathering of common useful ViewModels for usage in the XML layout.
Installation
composer require yireo/magento2-common-view-models
bin/magento module:enable Yireo_CommonViewModels
Roadmap
There is no roadmap. Feel free to open an Issue to request creation of a new ViewModel or enhancement of an existing ViewModel. Feel free to submit PRs. I'll treat it respectfully once I drink my morning coffee.
Generic usage of ViewModels
In Magento 2.2.1 or newer, create a XML layout instruction:
<block name="example" template="example.phtml">
<arguments>
<argument name="example_view_model" xsi:type="object">Yireo\CommonViewModels\ViewModel\Example</argument>
</arguments>
</block>
In your example.phtml:
<?php
/** @var \Yireo\CommonViewModels\ViewModel\Example $viewModel */
$exampleViewModel = $block->getExampleViewModel();
?>
Yireo\CommonViewModels\ViewModel\Product
Initialize the product with the data you have:
$productViewModel->setProduct($product);
$productViewModel->setProductById($productId);
$productViewModel->setProductBySku($productSku);
And then use it:
$productViewModel->getProduct();
$productViewModel->getSku();
Yireo\CommonViewModels\ViewModel\CurrentProduct
Only working when the page is catalog/product/view and when the id is set in the URL. Initialize it with the request first:
$currentProductViewModel->initialize();
And then use it:
$currentProductViewModel->getProduct();
$currentProductViewModel->getSku();
The CurrentProduct ViewModel extends the Product ViewModel through injection.
Yireo\CommonViewModels\ViewModel\Products
Use existing filters:
$productsViewModel->getProductsByName('%hoodie%');
$productsViewModel->getProductsBySku('B01%');
or build your own:
$searchCriteriaBuilder = $productsViewModel->getSearchCriteriaBuilder();
$productsViewModel->getProducts($searchCriteriaBuilder->create());
Yireo\CommonViewModels\ViewModel\FormKey
Usage:
$formkeyViewModel->getToken();
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
[Unreleased]
[0.0.2] - 29 July 2020
Added
- Magento 2.4 compatibility
[0.0.1] - Undocumented
Requires 3
| Package | Constraint |
|---|---|
| magento/module-catalog | ^102.0|^103.0|^104.0 |
| magento/framework | ^102.0|^103.0 |
| php | >=7.2.0 |
Requires-dev 2
| Package | Constraint |
|---|---|
| phpunit/phpunit | * |
| composer/composer | *@dev |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge. A phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
More from yireo
View vendorReplace bundled third party packages from Magento
N/A
Turn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.