scandipwa / route717

scandipwa/route717

ScandiPWA dedicated router

magento2-module Compatibility: Not compatible Code Quality: Fail Tests: N/A Security: Pass OSL-3.0

Are you the maintainer of scandipwa?

Packagento pulls scandipwa's Composer packages from the public registry so buyers can find them here.

Claim the namespace to take ownership, publish new releases directly, and start charging for premium versions.

Claim this namespace →

ScandiPWA Route717

Module is providing custom router to properly resolve HTTP codes on specific page request.

v1.1.0 update

Custom router is now checking theme type in order to support URL rewrites.
You must ensure PWA theme type is set to 4 to utilize the options.

Installer is doing this automatically for any newly generated theme.

For already generated theme please update manually: set PWA theme type to 4 in theme table.

Installation

composer require scandipwa/route717

Description

Module is providing validators for such entities:

  1. Product (/product)
  2. Category (/category)
  3. Cms pages (/page)
  4. Cart (/cart)
  5. Root (/)

How it works

Each frontend path (Magento 2 front name) should be added to validator list in src/etc/di.xml. Depending on entity
type it might have more or less complex validation logic, to i.e. determine if specific product exists or not.
Router is only responding 200 OK to entities, which it was able to validate. Otherwise it is falling back to default
Magento 2 routers.

Customization

To add new path you must provide your own validator, that must implement ScandiPWA\Router\ValidatorInterface and
register it as an array element passed to ScandiPWA\Router\ValidationManager using di.xml.

Accessing Magento 2 default routes

In order to allow Magento 2 to handle some routes in default manner (only serverside functionality) you must allow
specific routes to be accessed by adding RegExp to src/app/etc/di.xml::ignoredURLs arguments list.

So far there are 3 paths whitelisted out of the box:

  • /newsletter/subscriber/confirm - subscribe to newsletter
  • /newsletter/subscriber/unsubscribe - unsubscribe to newsletter
  • /customer/account/confirm/ - confirm e-mail (redirect to homepage in any case, modify according to your needs)

No changelog yet

The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.

Versions
Version Stability QA Status Compatibility Released
2.1.6 stable Fail Not compatible Details 2024-04-04 09:14:47
2.1.5 stable Not tested Not yet tested Details 2023-04-10 23:33:56
2.1.4 stable Not tested Not yet tested Details 2023-02-20 15:58:10
2.1.3 stable Not tested Not yet tested Details 2023-02-14 16:54:00
2.1.2 stable Not tested Not yet tested Details 2023-02-10 13:39:05
2.1.1 stable Not tested Not yet tested Details 2023-01-11 11:25:33
2.1.0 stable Not tested Not yet tested Details 2023-01-10 12:39:57
2.0.2 stable Not tested Not yet tested Details 2021-12-09 21:15:32
2.0.1 stable Not tested Not yet tested Details 2021-09-28 19:43:47
2.0.0 stable Not tested Not yet tested Details 2020-11-19 14:00:34
1.8.0 stable Not tested Not yet tested Details 2020-09-07 10:32:08
1.7.0 stable Not tested Not yet tested Details 2020-08-25 09:29:22
1.6.2 stable Not tested Not yet tested Details 2020-06-15 13:31:27
1.6.1 stable Not tested Not yet tested Details 2020-04-08 08:09:00
1.6.0 stable Not tested Not yet tested Details 2020-04-03 14:32:36
1.5.0 stable Not tested Not yet tested Details 2020-01-21 15:13:56
1.4.2 stable Not tested Not yet tested Details 2019-10-19 17:14:15
1.4.1 stable Not tested Not yet tested Details 2019-10-19 17:00:57
1.4.0 stable Not tested Not yet tested Details 2019-10-19 16:25:30
1.3.0 stable Not tested Not yet tested Details 2019-09-12 08:29:38
1.2.0 stable Not tested Not yet tested Details 2019-07-29 11:42:16
1.1.2 stable Not tested Not yet tested Details 2019-07-23 11:52:07
1.1.1 stable Not tested Not yet tested Details 2019-06-25 09:41:51
1.1.0 stable Not tested Not yet tested Details 2019-05-10 10:00:16
1.0.0 stable Not tested Not yet tested Details 2019-03-26 10:19:34

Requires 5

Package Constraint
magento/framework *
magento/module-customer *
magento/module-store *
magento/module-url-rewrite *
magento/module-wishlist *

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.

Compatibility matrix (Magento × PHP)
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Fail di error not tested
2.4.8 not tested not tested
2.4.9 Fail di error Fail di error

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.

Static analysis results
Tool Status Findings Summary
PHPCS Warning 52 52 warnings (ruleset: Magento2) — 24 auto-fixable with phpcbf
PHPMD Warning 7 7 rule violations (MissingImport:2, UnusedFormalParameter:1, ExcessiveClassComplexity:1, ExcessiveParameterList:1, TooManyFields:1)
Cpd Pass 0
Composer validate Info 5 valid; 5 advisory notes (composer validate --strict)

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.

PHPStan results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 72 72
2.4.8 72 75
2.4.9 75 75

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

Unit tests results by Magento and PHP version
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

Integration tests results by Magento and PHP version
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.

Security results
Tool Status Findings Summary
Composer audit Pass 0
Malware scan Pass 0
License
OSL-3.0

More from scandipwa

View vendor
Make it pay

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.