Home
Docs
GitHub
Pricing
Blog
Log In

Run Sandworm Audit for your App

Get started
Hold on, we're currently generating a fresh version of this report
This package has been abandoned.
Generated on May 5, 2024 via composer

laminas/laminas-zendframework-bridge 1.8.0

Alias legacy ZF class names to Laminas Project equivalents.
Package summary
Share
1
issue
1
high severity
meta
1
1
license
1
BSD-3-Clause
Package created
27 Mar 2019
Version published
24 Nov 2023
Maintainers
1
Total deps
1
Direct deps
0
License
BSD-3-Clause

Issues

1

1 high severity issue

high
via: laminas/laminas-zendframework-bridge@1.8.0
Collapse
Expand

Licenses

BSD 3-Clause "New" or "Revised" License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
place-warranty
Cannot
use-trademark
hold-liable
Must
include-copyright
include-license
1 Packages, Including:
laminas/laminas-zendframework-bridge@1.8.0
Disclaimer

This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license before using the licensed material.

Sandworm is not a law firm and does not provide legal services. Distributing, displaying, or linking to this deed or the license that it summarizes does not create a lawyer-client or any other relationship.

Direct Dependencies

0
All Dependencies CSV
β“˜ This is a list of laminas/laminas-zendframework-bridge 's direct dependencies. Data on all dependencies, including transitive ones, is available via CSV download.
NameVersionSizeLicenseTypeVulnerabilities

Visualizations

Frequently Asked Questions

What does laminas/laminas-zendframework-bridge do?

The laminas/laminas-zendframework-bridge is an advanced PHP package that provides a crucial role of linking legacy Zend Framework, Apigility, and Expressive classes to their replacements under the Laminas Project. This offers seamless transitioning without affecting the performance of existing projects. It's important to note that this package is utilized in conjunction with the composer plugin that installs Laminas packages in place of ZF/Apigility/Expressive packages. It supports Zend Framework MVC projects, Apigility projects, and Expressive versions.

How do you use laminas/laminas-zendframework-bridge?

Utilizing the laminas/laminas-zendframework-bridge package in your project is quite straightforward. You should start by installing the library. This can be achieved by running the below command in your terminal:

$ composer require laminas/laminas-zendframework-bridge

Once the installation is complete, you may need to provide additional replacements for the configuration post processor, especially if your application uses third-party components that includes class names that the post processor rewrites.

For instance:

return [
    'laminas-zendframework-bridge' => [
        'replacements' => [
            'to-replace' => 'replacement',
            // ...
        ],
    ],
];

Here is a practical example, if your configuration included the following dependency mapping:

return [
    'controller_plugins' => [
        'factories' => [
            'customZendFormBinder' => \CustomZendFormBinder\Controller\Plugin\Factory\BinderPluginFactory::class,
        ],
    ],
];

And you wanted the two strings that contain the verbiage ZendForm to remain untouched, you could define the following replacements mapping:

return [
    'laminas-zendframework-bridge' => [
        'replacements' => [
            // Never rewrite!
            'customZendFormBinder' => 'customZendFormBinder',
            'CustomZendFormBinder' => 'CustomZendFormBinder',
        ],
    ],
];

Where are the laminas/laminas-zendframework-bridge docs?

The official documentation for the laminas/laminas-zendframework-bridge package is primarily contained within the provided README file on the package's GitHub repository. Additional support and discussions can be found on the Laminas forum. For reporting issues and bugs, there's the issues page on the package's GitHub repository.