yireo / magento2-additional-endpoints-graph-ql
yireo/magento2-additional-endpoints-graph-ql
Additional GraphQL endpoints for Magento 2
This module offers some additional endpoints for loading information through GraphQL.
Installation
Use the following commands to install this module into Magento 2:
composer require magento2-additional-endpoints-graph-ql:@dev
bin/magento module:enable Yireo_AdditionalEndpointsGraphQl
bin/magento setup:upgrade
productById(Int id) - Get a product by its ID
Example:
{
productById(id:42){
sku
name
}
}
productBySku(String! sku) - Get a product by its SKU
Example:
{
productBySku(sku:"VA22-SI-NA"){
sku
name
}
}
categoryById(Int id) - Get a category by its ID
Example:
{
categoryById(id:1){
id
name
}
}
cmsBlock(String! identifier) - Get a CMS block by its identifier
Example:
{
cmsBlock(identifier:"example"){
title
content
}
}
cmsPages - Get all CMS pages
Example:
{
cmsPages {
items {
title
}
}
}
cmsWidget(Int! id) - Get a CMS widget by its ID
Example:
{
cmsWidget(id: "2") {
id
title
html
parameters {
name
value
}
}
}
validateCustomerToken - Validate a customer token
Example:
query validateToken {
validateCustomerToken(token:"abc")
}
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
Requires 5
| Package | Constraint |
|---|---|
| magento/framework | ^102.0|^103.0 |
| magento/module-catalog | ^101.0|^102.0|^103.0|^104.0 |
| magento/module-cms | ^101.0|^102.0|^103.0|^104.0 |
| magento/module-graph-ql | ^100.0 |
| php | >=7.0.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.
PHPStan
Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases.
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
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
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.