laminas/laminas-zendframework-bridge
Provides compatibility bridge for Laminas to ease migration from Zend Framework. Maps legacy Zend class names to Laminas equivalents via autoloading, allowing existing Zend-based apps and libraries to run with minimal changes during upgrades.
Feature release (minor)
Feature release (minor)
1.6.x bugfix release (patch)
Feature release (minor)
Feature release (minor)
1.4.x bugfix release (patch)
Feature release (minor)
1.2.x bugfix release (patch)
Feature release (minor)
COMPOSER_VENDOR_DIR env variable is missing or empty. Previously, this could lead to scenarios where a non-existent path was used for finding the bridge autoloader.COMPOSER_VENDOR_DIR before trying to resolve relative to where the package is installed.Release 1.1.0
#63 fixes handling of dependency configuration to ensure each of delegators, initializers, and abstract factories are properly handled during configuraiton post processing. The new approach should allow delegators to work post-migration to Laminas or Mezzio.
#61 ensures configuration for delegator factories gets rewritten; the functionality broke in version 1.0.1.
#55 adds provisions to ensure that references to legacy classes/interfaces in dependency configuration always create aliases from the legacy to the new classes. Previously, we did straight replacements in the configuration, which could lead to the legacy service no longer being available. Now it will remain available.
#59 fixes the replacement rules such as to avoid replacing references to API Skeletons packages, classes, or configuration keys.
#57 fixes how references to the "zf-apigility" key are replaced. Previously, they were rewritten to "laminas-api-tools", but the correct replacement is "api-tools".
#56 provides a mechanism to add additional maps with multiple levels of namespace separator escaping, in order to ensure that all various known permutations are matched. The escaping is applied to both the original and target, to ensure that rewrites conform to the original escaping.
#56 makes changes to the replacement rules to ensure we do not replace references to "Zend" or "ZF" if they occur as subnamespaces OR as class names (formerly, we only enforced subnamespaces). Additional rules were provided for cases where one or both occur within our own packages.
#52 fixes a scenario whereby factory values were not being rewritten during configuration post processing.
#52 fixes an issue that occurs with the configuration post processor. Previously, when a service name used as a factory or invokable was encountered that referenced a legacy class, it would get rewritten. This would cause issues if the service was not exposed in the original legacy package, however, as there would now be no alias of the legacy service to the new one. This patch modifies the configuration post processor such that it now tests to see if a service name it will rename exists as an alias; if not, it also creates the alias.
#47 adds entries for rewriting the various ::*Zend() methods exposed in the psr7bridge to ::*Laminas() during migrations.
#46 adds a rule to rewrite the config key use_zend_loader to use_laminas_loader.
#45 adds a rule to exclude rewriting of view paths provided by the various Doctrine modules targeting the developer tools.
ZendServerDisk, ZendServerShm, ZendMonitor).Northwoods\Container\Zend\Config was incorrectly being renamed to Northwoods\Container\Laminas\Config (which should not happen, as it is not a class under our control).#32 changes all references to Expressive to instead reference Mezzio.
#32 changes all references to Apigility to instead reference Laminas API Tools. The vendor becomes laminas-api-tools, the URL becomes api-tools.getlaminas.org, packages and repos are prefixed with api-tools, and namespaces become Laminas\ApiTools.
ZendDeveloperTools to Laminas\DeveloperTools, and vice-versa.zenddevelopertools string to rewrite to laminas-developer-tools instead of laminasdevelopertools.EVENT_MERGE_CONFIG listener (for use with MVC applications). When registered, it will post-process the configuration, replacing known Zend Framework-specific strings with their Laminas replacements. A ruleset is provided that ensures dependency configuration is rewritten in a safe manner, routing configuration is skipped, and certain top-level configuration keys are matched exactly (instead of potentially as substrings or word stems). A later release of laminas-migration will auto-register these tools in applications when possible.#21 removes rewriting of the Amazon library, as it is not moving to Laminas.
#21 removes rewriting of the GCM and APNS libraries, as they are not moving to Laminas.
How can I help you explore Laravel packages today?