All notable changes to this project will be documented in this file, in reverse chronological order by release.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- #34 changes suggested version of laminas-auradi-config to 2.0.
- Nothing.
- Nothing.
-
#39 fixes the factories for the
NotFoundHandlerandErrorResponseGeneratorto castnulllayout values from configuration to empty strings. -
zendframework/zend-expressive#663 fixes parameter types in docblock for
Mezzio\MiddlewareFactory::pipeline()
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- zendframework/zend-expressive#646 fixes behavior in the
MiddlewareContainerwhen retrieving services that implement bothRequestHandlerInterfaceandMiddlewareInterface. Previously, it incorrectly cast these values toRequestHandlerMiddleware, which could cause middleware pipelines to fail if they attempted to delegate back to the application middleware pipeline. These values are now correctly returned verbatim.
- zendframework/zend-expressive#637 adds support for zendframework/zend-diactoros 2.0.0. You may use either a 1.Y or 2.Y version of that library with Expressive applications.
- Nothing.
- Nothing.
- Nothing.
- zendframework/zend-expressive#634 provides several minor performance and maintenance improvements.
- Nothing.
- zendframework/zend-expressive#629 changes the constructor of
Mezzio\Middleware\ErrorResponseGeneratorto accept an additional, optional argument,$layout, which defaults to a new constant value,ErrorResponseGenerator::LAYOUT_DEFAULT, orlayout::default.Mezzio\Container\ErrorResponseGeneratorFactorynow also looks for the configuration valuemezzio.error_handler.layout, and will use that value to seed the constructor argument. This change makes theErrorResponseGeneratormirror theNotFoundHandler, allowing for a consistent layout between the two error pages.
- Nothing.
- Nothing.
- Nothing.
- zendframework/zend-expressive#615 adds a cookbook entry for accessing common data in templates.
- Nothing.
- Nothing.
- Nothing.
- zendframework/zend-expressive#627 fixes an issue in the Whoops response generator; previously, if an error or
exception occurred in an
ErrorHandlerlistener or prior to handling the pipeline, Whoops would fail to intercept, resulting in an empty response with status 200. With the patch, it properly intercepts and displays the errors.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- zendframework/zend-expressive#612 updates the
ApplicationConfigInjectionDelegatordelegator factory logic to cast the$configvalue to an array before passing it to itsinjectPipelineFromConfig()andinjectRoutesFromConfig()methods, ensuring it will work correctly with containers that store theconfigservice as anArrayObjectinstead of anarray.
- Nothing.
- zendframework/zend-expressive#596 updates the
ApplicationConfigInjectionDelegator::injectRoutesFromConfig()method to use the key name associated with a route specification if nonamemember is provided when creating aRouteinstance. This can help enforce name uniqueness when defining routes via configuration.
- Nothing.
- Nothing.
- Nothing.
-
zendframework/zend-expressive#543 adds support for the final PSR-15 interfaces, and explicitly depends on psr/http-server-middleware.
-
zendframework/zend-expressive#538 adds scalar and return type hints to methods wherever possible.
-
zendframework/zend-expressive#562 adds the class
Mezzio\Response\ServerRequestErrorResponseGenerator, and maps it to theMezzio\Container\ServerRequestErrorResponseGeneratorFactory. The class generates an error response when an exeption occurs producing a server request instance, and can be optionally templated. -
zendframework/zend-expressive#543 adds a new class,
Mezzio\MiddlewareContainer. The class decorates a PSR-11ContainerInterface, and adds the following behavior:- If a class is not in the container, but exists,
has()will returntrue. - If a class is not in the container, but exists,
get()will attempt to instantiate it, caching the instance locally if it is valid. - Any instance pulled from the container or directly instantiated is tested.
If it is a PSR-15
RequestHandlerInterface, it will decorate it in a laminas-stratigilityRequestHandlerMiddlewareinstance. If the instance is not a PSR-15MiddlewareInterface, the container will raise aMezzio\Exception\InvalidMiddlewareException.
- If a class is not in the container, but exists,
-
zendframework/zend-expressive#543 adds a new class,
Mezzio\MiddlewareFactory. The class composes aMiddlewareContainer, and exposes the following methods:callable(callable $middleware) : CallableMiddlewareDecoratorhandler(RequestHandlerInterface $handler) : RequestHandlerMiddlewarelazy(string $service) : LazyLoadingMiddlewareprepare($middleware) : MiddlewareInterface: accepts a string service name, callable,RequestHandlerInterface,MiddlewareInterface, or array of such values, and returns aMiddlewareInterface, raising an exception if it cannot determine what to do.pipeline(...$middleware) : MiddlewarePipe: passes each argument toprepare(), and the result toMiddlewarePipe::pipe(), returning the pipeline when complete.
-
zendframework/zend-expressive#543 adds the following factory classes, each within the
Mezzio\Containernamespace:ApplicationPipelineFactory: creates and returns aLaminas\Stratigility\MiddlewarePipeto use as the application middleware pipeline.DispatchMiddlewareFactory: creates and returns aMezzio\Router\DispatchMiddlewareinstance.EmitterFactory: creates and returns aLaminas\HttpHandlerRunner\Emitter\EmitterStackinstance composing anSapiEmitterfrom that same namespace as the only emitter on the stack. This is used as a dependency for theLaminas\HttpHandlerRunner\RequestHandlerRunnerservice.MiddlewareContainerFactory: creates and returns aMezzio\MiddlewareContainerinstance decorating the PSR-11 container passed to the factory.MiddlewareFactoryFactory: creates and returns aMezzio\MiddlewareFactoryinstance decorating aMiddlewareContainerinstance as pulled from the container.RequestHandlerRunnerFactory: creates and returns aLaminas\HttpHandlerRunner\RequestHandlerRunnerinstance, using the servicesMezzio\Application,Laminas\HttpHandlerRunner\Emitter\EmitterInterface,Mezzio\ServerRequestFactory, andMezzio\ServerRequestErrorResponseGenerator.ServerRequestFactoryFactory: creates and returns acallablefactory for generating a PSR-7ServerRequestInterfaceinstance; this returned factory is a dependency for theLaminas\HttpHandlerRunner\RequestHandlerRunnerservice.ServerRequestErrorResponseGeneratorFactory: creates and returns acallablethat accepts a PHPThrowablein order to generate a PSR-7ResponseInterfaceinstance; this returned factory is a dependency for theLaminas\HttpHandlerRunner\RequestHandlerRunnerservice, which uses it to generate a response in the scenario that theServerRequestFactoryis unable to create a request instance.
-
zendframework/zend-expressive#551 and zendframework/zend-expressive#554 add the following constants under the
Mezzionamespace:DEFAULT_DELEGATEcan be used to refer to the formerDefaultDelegateFQCN service, and maps to theMezzio\Handler\NotFoundHandlerservice.IMPLICIT_HEAD_MIDDLEWAREcan be used to refer to the formerMezzio\Middleware\ImplicitHeadMiddlewareservice, and maps to theMezzio\Router\Middleware\ImplicitHeadMiddlewareservice.IMPLICIT_OPTIONS_MIDDLEWAREcan be used to refer to the formerMezzio\Middleware\ImplicitOptionsMiddlewareservice, and maps to theMezzio\Router\Middleware\ImplicitOptionsMiddlewareservice.NOT_FOUND_MIDDLEWAREcan be used to refer to the formerMezzio\Middleware\NotFoundMiddlewareservice, and maps to theMezzio\Handler\NotFoundHandlerservice.
-
zendframework/zend-expressive#579 updates the version constraint for mezzio-router to use 3.0.0rc4 or later.
-
zendframework/zend-expressive#579 updates the version constraint for laminas-stratigility to use 3.0.0rc1 or later.
-
zendframework/zend-expressive#543 adds a dependency on zendframework/zend-httphandlerrunner 1.0.0
-
zendframework/zend-expressive#542 modifies the
composer.jsonto no longer suggest the pimple/pimple package, but rather the zendframework/zend-pimple-config package. -
zendframework/zend-expressive#542 modifies the
composer.jsonto no longer suggest the aura/di package, but rather the zendframework/zend-auradi-config package. -
zendframework/zend-expressive#543 updates the
Mezzio\ConfigProviderto reflect new, removed, and updated services and their factories. -
zendframework/zend-expressive#554 updates the
ConfigProviderto add entries for the following constants as follows:IMPLICIT_HEAD_MIDDLEWAREaliases to theMezzio\Router\Middleware\ImplicitHeadMiddlewareservice.IMPLICIT_OPTIONS_MIDDLEWAREaliases to theMezzio\Router\Middleware\ImplicitOptionsMiddlewareservice.
-
zendframework/zend-expressive#543 updates
Mezzio\Handler\NotFoundHandlerto implement the PSR-15RequestHandlerInterface. AsMezzio\Middleware\NotFoundHandleris removed,Mezzio\Container\NotFoundHandlerFactoryhas been re-purposedto create an instance ofMezzio\Handler\NotFoundHandler. -
zendframework/zend-expressive#561 modifies the
Mezzio\Handler\NotFoundHandlerto compose a response factory instead of a response prototype. -
zendframework/zend-expressive#543 refactors
Mezzio\Applicationcompletely.The class no longer extends
Laminas\Stratigility\MiddlewarePipe, and instead implements the PSR-15MiddlewareInterfaceandRequestHandlerInterface.It now requires the following dependencies via constructor injection, in the following order:
Mezzio\MiddlewareFactoryLaminas\Stratigility\MiddlewarePipe; this is the pipeline representing the application.Mezzio\Router\RouteCollectorLaminas\HttpHandlerRunner\RequestHandlerRunner
It removes all "getter" methods (as detailed in the "Removed" section of this release), but retains the following methods, with the changes described below. Please note: in most cases, these methods accept the same arguments as in the version 2 series, with the exception of callable double-pass middleware (these may be decorated manually using
Laminas\Stratigility\doublePassMiddleware()), and http-interop middleware (no longer supported; rewrite as PSR-15 middleware).-
pipe($middlewareOrPath, $middleware = null) : voidpasses its arguments to the composedMiddlewareFactory'sprepare()method; if two arguments are provided, the second is passed to the factory, and the two together are passed toLaminas\Stratigility\path()in order to decorate them to work as middleware. The prepared middleware is then piped to the composedMiddlewarePipeinstance.As a result of switching to use the
MiddlewareFactoryto prepare middleware, you may now pipeRequestHandlerInterfaceinstances as well. -
route(string $path, $middleware, array $methods = null, string $name) : Routepasses its$middlewareargument to theMiddlewareFactory::prepare()method, and then all arguments to the composedRouteCollectorinstance'sroute()method.As a result of switching to use the
MiddlewareFactoryto prepare middleware, you may now route toRequestHandlerInterfaceinstances as well. -
Each of
get,post,patch,put,delete, andanynow proxy toroute()after marshaling the correct$methods. -
getRoutes() : Route[]proxies to the composedRouteCollectorinstance. -
handle(ServerRequestInterface $request) : ResponseInterfaceproxies to the composedMiddlewarePipeinstance'shandle()method. -
process(ServerRequestInterface $request, RequestHandlerInterface $handler) : ResponseInterfaceproxies to the composedMiddlewarePipeinstance'sprocess()method. -
run() : voidproxies to the composedRequestHandlerRunnerinstance. Please note that the method no longer accepts any arguments.
-
zendframework/zend-expressive#543 modifies the
Mezzio\Container\ApplicationFactoryto reflect the changes to theMezzio\Applicationclass as detailed above. It pulls the following services to inject via the constructor:Mezzio\MiddlewareFactoryLaminas\Stratigility\ApplicationPipeline, which should resolve to aMiddlewarePipeinstance; use theMezzio\Container\ApplicationPipelineFactory.Mezzio\Router\RouteCollectorLaminas\HttpHandlerRunner\RequestHandlerRunner
-
zendframework/zend-expressive#581 changes how the
ApplicationConfigInjectionDelegator::injectPipelineFromConfig()method works. Previously, it would auto-inject routing and dispatch middleware if routes were configured, but nomiddleware_pipelinewas present. Considering that this method will always be called manually, this functionality was removed; the method now becomes a no-op if nomiddleware_pipelineis present. -
zendframework/zend-expressive#568 updates the
ErrorHandlerFactoryto pull thePsr\Http\Message\ResponseInterfaceservice, which returns a factory capable of returning a response instance, and passes it to theLaminas\Stratigility\Middleware\ErrorHandlerinstance it creates, as that class changes in 3.0.0alpha4 such that it now expects a factory instead of an instance. -
zendframework/zend-expressive#562 extracts most logic from
Mezzio\Middleware\ErrorResponseGeneratorto a new trait,Mezzio\Response\ErrorResponseGeneratorTrait. A trait was used as the classes consuming it are from different namespaces, and thus different inheritance trees. The trait is used by both theErrorResponseGeneratorand the newServerRequestErrorResponseGenerator. -
zendframework/zend-expressive#551 removes
Mezzio\Container\RouteMiddlewareFactory, as mezzio-router now provides a factory for the middleware. -
zendframework/zend-expressive#551 removes
Mezzio\Container\DispatchMiddlewareFactory, as mezzio-router now provides a factory for the middleware. -
zendframework/zend-expressive#551 removes
Mezzio\Middleware\ImplicitHeadMiddleware, as it is now provided by the mezzio-router package. -
zendframework/zend-expressive#551 removes
Mezzio\Middleware\ImplicitOptionsMiddleware, as it is now provided by the mezzio-router package.
- Nothing.
-
zendframework/zend-expressive#529 removes support for PHP versions prior to PHP 7.1.
-
zendframework/zend-expressive#529 removes support for http-interop/http-middleware (previous PSR-15 iteration).
-
zendframework/zend-expressive#543 removes support for http-interop/http-server-middleware.
-
zendframework/zend-expressive#580 removes laminas-diactoros as a requirement; all usages of it within the package are currently conditional on it being installed, and can be replaced easily with any other PSR-7 implementation at this time.
-
zendframework/zend-expressive#543 removes the class
Mezzio\Delegate\NotFoundDelegate; useMezzio\Handler\NotFoundHandlerinstead. -
zendframework/zend-expressive#546 removes the service
Mezzio\Delegate\DefaultDelegate, as there is no longer a concept of a default handler invoked by the application. Instead, developers MUST pipe a request handler or middleware at the innermost layer of the pipeline guaranteed to return a response; we recommend usingMezzio\Handler\NotFoundHandlerfor this purpose. -
zendframework/zend-expressive#543 removes the class
Mezzio\Middleware\RouteMiddleware. Use theRouteMiddlewarefrom mezzio-router instead. -
zendframework/zend-expressive#543 removes the class
Mezzio\Middleware\DispatchMiddleware. Use theDispatchMiddlewarefrom mezzio-router instead; the factoryMezzio\Container\DispatchMiddlewareFactorywill return an instance for you. -
zendframework/zend-expressive#543 removes the class
Mezzio\Emitter\EmitterStack; use the classLaminas\HttpHandlerRunner\Emitter\EmitterStackinstead. -
zendframework/zend-expressive#543 removes the following methods from
Mezzio\Application:pipeRoutingMiddleware(): usepipe(\Mezzio\Router\RouteMiddleware::class)instead.pipeDispatchMiddleware(): usepipe(\Mezzio\Router\DispatchMiddleware::class)instead.getContainer()getDefaultDelegate(): ensure you pipe middleware or a request handler capable of returning a response at the innermost layer;Mezzio\Handler\NotFoundHandlercan be used for this.getEmitter(): use theLaminas\HttpHandlerRunner\Emitter\EmitterInterfaceservice from the container.injectPipelineFromConfig(): use the newApplicationConfigInjectionDelegatorand/or the static method of the same name it defines.injectRoutesFromConfig(): use the newApplicationConfigInjectionDelegatorand/or the static method of the same name it defines.
-
zendframework/zend-expressive#543 removes the class
Mezzio\AppFactory. -
The internal
Mezzio\MarshalMiddlewareTrait,Mezzio\ApplicationConfigInjectionTrait, andMezzio\IsCallableMiddlewareTraithave been removed.
- zendframework/zend-expressive#574 updates the
classes
Mezzio\Exception\InvalidMiddlewareExceptionandMissingDependencyExceptionto implement the PSR-11ContainerExceptionInterface.
-
zendframework/zend-expressive#581 adds the class
Mezzio\ConfigProvider, and exposes it to the laminas-component-installer Composer plugin. We recommend updating yourconfig/config.phpto reference it, as well as theMezzio\Router\ConfigProvidershipped with mezzio-router versions 2.4 and up. -
zendframework/zend-expressive#581 adds the class
Mezzio\Container\ApplicationConfigInjectionDelegator. The class can act as a delegator factory, and, when enabled, will inject routes and pipeline middleware defined in configuration.Additionally, the class exposes two static methods:
injectPipelineFromConfig(Application $app, array $config)injectRoutesFromConfig(Application $app, array $config)
These may be called to modify an
Applicationinstance based on an array of configuration. See thd documentation for more details. -
zendframework/zend-expressive#581 adds the class
Mezzio\Handler\NotFoundHandler; the class takes over the functionality previously provided inMezzio\Delegate\NotFoundDelegate.
-
zendframework/zend-expressive#581 updates the minimum supported laminas-stratigility version to 2.2.0.
-
zendframework/zend-expressive#581 updates the minimum supported mezzio-router version to 2.4.0.
-
zendframework/zend-expressive#581 deprecates the following classes and traits:
-
Mezzio\AppFactory: if you are using this, you will need to switch to direct usage ofMezzio\Applicationor aLaminas\Stratigility\MiddlewarePipeinstance. -
Mezzio\ApplicationConfigInjectionTrait: if you are using it, it is marked internal, and deprecated; it will be removed in version 3. -
Mezzio\Container\NotFoundDelegateFactory: theNotFoundDelegatewill be renamed toMezzio\Handler\NotFoundHandlerin version 3, making this factory obsolete. -
Mezzio\Delegate\NotFoundDelegate: this class becomesMezzio\Handler\NotFoundHandlerin v3, and the new class is added in version 2.2 as well. -
Mezzio\Emitter\EmitterStack: the emitter concept is extracted from laminas-diactoros to a new component, laminas-httphandlerrunner. This latter component is used in version 3, and defines theEmitterStackclass. Unless you are extending it or interacting with it directly, this change should not affect you; theLaminas\Diactoros\Response\EmitterInterfaceservice will be directed to the new class in that version. -
Mezzio\IsCallableInteropMiddlewareTrait: if you are using it, it is marked internal, and deprecated; it will be removed in version 3. -
Mezzio\MarshalMiddlewareTrait: if you are using it, it is marked internal, and deprecated; it will be removed in version 3. -
Mezzio\Middleware\DispatchMiddleware: this functionality has been moved to mezzio-router, under theMezzio\Router\Middlewarenamespace. -
Mezzio\Middleware\ImplicitHeadMiddleware: this functionality has been moved to mezzio-router, under theMezzio\Router\Middlewarenamespace. -
Mezzio\Middleware\ImplicitOptionsMiddleware: this functionality has been moved to mezzio-router, under theMezzio\Router\Middlewarenamespace. -
Mezzio\Middleware\NotFoundHandler: this will be removed in version 3, where you can instead pipeMezzio\Handler\NotFoundHandlerdirectly instead. -
Mezzio\Middleware\RouteMiddleware: this functionality has been moved to mezzio-router, under theMezzio\Router\Middlewarenamespace.
-
-
zendframework/zend-expressive#581 deprecates the following methods from
Mezzio\Application:pipeRoutingMiddleware()pipeDispatchMiddleware()getContainer(): this method is removed in version 3; container access will only be via the bootstrap.getDefaultDelegate(): the concept of a default delegate is removed in version 3.getEmitter(): emitters move to a different collaborator in version 3.injectPipelineFromConfig()anddinjectRoutesFromConfig()are methods defined by theApplicationConfigInjectionTrait, which will be removed in version 3. Use theApplicationConfigInjectionDelegatorinstead.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
-
zendframework/zend-expressive#583 provides a number of minor fixes and test changes to ensure the component works with the mezzio-router 2.4 version. In particular, configuration-driven routes will now work properly across all versions, without deprecation notices.
-
zendframework/zend-expressive#582 fixes redirects in the documentation.
- zendframework/zend-expressive#480 updates the
ImplicitHeadMiddlewareto add a request attribute indicating the request was originally generated for aHEADrequest before delegating the request; you can now pull the attributeMezzio\Middleware\ImplicitHeadMiddleware::FORWARDED_HTTP_METHOD_ATTRIBUTEin your own middleware in order to vary behavior in these scenarios.
-
zendframework/zend-expressive#505 modifies
Mezzio\Applicationto remove implementation of__call()in favor of the following new methods:get($path, $middleware, $name = null)post($path, $middleware, $name = null)put($path, $middleware, $name = null)patch($path, $middleware, $name = null)delete($path, $middleware, $name = null)
This change is an internal implementation detail only, and will not affect existing implementations or extensions.
-
zendframework/zend-expressive#511 modifies the
NotFoundDelegateto accept an optional$layoutargument to its constructor; the value defaults tolayout::defaultif not provided. That value will be passed for thelayouttemplate variable when the delegate renders a template, allowing laminas-view users (and potentially other template systems) to customize the layout template used for reporting errors.You may provide the template via the configuration
mezzio.error_handler.layout.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- zendframework/zend-expressive#534 provides a
fix for how it detects
callablemiddleware. Previously, it relied on PHP'sis_callable(), but that function can result in false positives when provided a 2-element array where the first element is an object, as the function does not verify that the second argument is a valid method of the first. We now implement additional verifications to prevent such false positives.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- zendframework/zend-expressive#521 adds an
explicit requirement on http-interop/http-middleware
^0.4.1to the package. This is necessary as newer builds of laminas-stratigility instead depend on the metapackage webimpress/http-middleware-compatibility instead of the http-interop/http-middleware package — but middleware shipped in Mezzio requires it. This addition fixes problems due to missing http-middleware interfaces.
- zendframework/zend-expressive#508 adds
documentation covering
Mezzio\Helper\ContentLengthMiddleware, introduced in mezzio-helpers 4.1.0.
- Nothing.
- Nothing.
- zendframework/zend-expressive#479 fixes the
WhoopsErrorResponseGenerator::$whoopsdockblock Type to support Whoops 1 and 2. - zendframework/zend-expressive#482 fixes the
Application::$defaultDelegatedockblock Type. - zendframework/zend-expressive#489 fixes an
edge case in the
WhoopsErrorHandlerwhereby it would emit an error if$_SERVER['SCRIPT_NAME']did not exist. It now checks for that value before attempting to use it.
- Nothing.
- zendframework/zend-expressive#468 updates
references to
DefaultDelegate::classto instead use the string'Mezzio\Delegate\DefaultDelegate'; using the string makes it clear that the service name does not resolve to an actual class.
- Nothing.
- Nothing.
- zendframework/zend-expressive#476 fixes the
WhoopsErrorResponseGeneratorto ensure it returns a proper error status code, instead of using a200 OKstatus.
- Nothing.
- Nothing.
- Nothing.
- zendframework/zend-expressive#467 fixes an
issue when passing invokable, duck-typed, interop middleware to the
application without registering it with the container. Prior to the patch, it
was incorrectly being decorated by
Laminas\Stratigility\Middleware\CallableMiddlewareWrapperinstead ofLaminas\Stratigility\Middleware\CallableInteropMiddlewareWrapper.
- Nothing.
- Nothing.
- Nothing.
- zendframework/zend-expressive#464 fixes the
WhoopsErrorResponseGeneratorto provide a correctContent-Typeheader to the response when a JSON request occurs.
-
zendframework/zend-expressive#450 adds support for PSR-11; Mezzio is now a PSR-11 consumer.
-
zendframework/zend-expressive#428 updates the laminas-stratigility dependency to require
^2.0; this allows usage of both the new middleare-based error handling system introduced in laminas-stratigility 1.3, as well as usage of http-interop/http-middleware implementations with Mezzio. The following middleware is now supported:- Implementations of
Interop\Http\ServerMiddleware\MiddlewareInterface. - Callable middleware that implements the same signature as
Interop\Http\ServerMiddleware\MiddlewareInterface. - Callable middleware using the legacy double-pass signature
(
function ($request, $response, callable $next)); these are now decorated inLaminas\Stratigility\Middleware\CallableMiddlewareWrapperinstances. - Service names resolving to any of the above.
- Arrays of any of the above; these will be cast to
Laminas\Stratigility\MiddlewarePipeinstances, piping each middleware.
- Implementations of
-
zendframework/zend-expressive#396 adds
Mezzio\Middleware\NotFoundHandler, which provides a way to return a templated 404 response to users. This middleware should be used as innermost middleware. You may use the newMezzio\Container\NotFoundHandlerFactoryto generate the instance via your DI container. -
zendframework/zend-expressive#396 adds
Mezzio\Container\ErrorHandlerFactory, for generating aLaminas\Stratigility\Middleware\ErrorHandlerto use with your application. If aMezzio\Middleware\ErrorResponseGeneratorservice is present in the container, it will be used to seed theErrorHandlerwith a response generator. If you use this facility, you should enable themezzio.raise_throwablesconfiguration flag. -
zendframework/zend-expressive#396 adds
Mezzio\Middleware\ErrorResponseGeneratorandMezzio\Middleware\WhoopsErrorResponseGenerator, which may be used withLaminas\Stratigility\Middleware\ErrorHandlerto generate error responses. The first will generate templated error responses if a template renderer is composed, and the latter will generate Whoops output. You may use the newMezzio\Container\ErrorResponseGeneratorFactoryandMezzio\Container\WhoopsErrorResponseGeneratorFactory, respectively, to create these instances; if you do, assign these to the service nameMezzio\Middleware\ErrorResponseGeneratorto have them automatically registered with theErrorHandler. -
zendframework/zend-expressive#396 adds
Mezzio\ApplicationConfigInjectionTrait, which exposes two methods,injectRoutesFromConfig()andinjectPipelineFromConfig(); this trait is now composed into theApplicationclass. These methods allow you to configure anApplicationinstance from configuration if desired, and are now used by theApplicationFactoryto configure theApplicationinstance. -
zendframework/zend-expressive#396 adds a vendor binary,
vendor/bin/mezzio-tooling, which will install (or uninstall) the mezzio-tooling; this package provides migration tools for updating your application to use programmatic pipelines and the new error handling strategy, as well as tools for identifying usage of the legacy Stratigility request and response decorators and error middleware. -
zendframework/zend-expressive#413 adds the middleware
Mezzio\Middleware\ImplicitHeadMiddleware; this middleware can be used to provide implicit support forHEADrequests when the matched route does not explicitly support the method. -
zendframework/zend-expressive#413 adds the middleware
Mezzio\Middleware\ImplicitOptionsMiddleware; this middleware can be used to provide implicit support forOPTIONSrequests when the matched route does not explicitly support the method; the returned 200 response will also include anAllowheader listing allowed HTTP methods for the URI. -
zendframework/zend-expressive#426 adds the method
Application::getRoutes(), which will return the list ofMezzio\Router\Routeinstances currently registered with the application. -
zendframework/zend-expressive#428 adds the class
Mezzio\Delegate\NotFoundDelegate, anInterop\Http\ServerMiddleware\DelegateInterfaceimplementation. The class will return a 404 response; if aTemplateRendererInterfaceis available and injected into the delegate, it will provide templated contents for the 404 response as well. We also provideMezzio\Container\NotFoundDelegateFactoryfor providing an instance. -
zendframework/zend-expressive#428 adds the method
Mezzio\Application::getDefaultDelegate(). This method will return the defaultInterop\Http\ServerMiddleware\DelegateInterfaceinjected during instantiation, or, if none was injected, lazy load an instance ofMezzio\Delegate\NotFoundDelegate. -
zendframework/zend-expressive#428 adds the constants
DISPATCH_MIDDLEWAREandROUTING_MIDDLEWAREtoMezzio\Application; they have identical values to the constants previously defined inMezzio\Container\ApplicationFactory. -
zendframework/zend-expressive#428 adds
Mezzio\Middleware\LazyLoadingMiddleware; this essentially extracts the logic previously used withinMezzio\Applicationto provide container-based middleware to allow lazy-loading only when dispatched.
-
zendframework/zend-expressive#440 changes the
Mezzio\Application::__call($method, array $args)signature; in previous versions,$argsdid not have a typehint. If you are extending the class and overriding this method, you will need to update your signature accordingly. -
zendframework/zend-expressive#428 updates
Mezzio\Container\ApplicationFactoryto ignore themezzio.raise_throwablesconfiguration setting; Stratigility 2.X no longer catches exceptions in its middleware dispatcher, making the setting irrelevant. -
zendframework/zend-expressive#422 updates the mezzio-router minimum supported version to 2.0.0.
-
zendframework/zend-expressive#428 modifies the
Mezzio\Container\ApplicationFactoryconstantsDISPATCH_MIDDLEWAREandROUTING_MIDDLEWAREto define themselves based on the constants of the same name now defined inMezzio\Application. -
zendframework/zend-expressive#428 modifies the constructor of
Mezzio\Application; the third argument was previously a nullable callable$finalHandler; it is now a nullableInterop\Http\ServerMiddleware\DelegateInterfacewith the name$defaultDelegate. -
zendframework/zend-expressive#450 modifies the signatures in several classes to typehint against PSR-11 instead of container-interop; these include:
Mezzio\AppFactory::create()Mezzio\Application::__construct()Mezzio\Container\ApplicationFactory::__invoke()Mezzio\Container\ErrorHandlerFactory::__invoke()Mezzio\Container\ErrorResponseGeneratorFactory::__invoke()Mezzio\Container\NotFoundDelegateFactory::__invoke()Mezzio\Container\NotFoundHandlerFactory::__invoke()Mezzio\Container\WhoopsErrorResponseGeneratorFactory::__invoke()Mezzio\Container\WhoopsFactory::__invoke()Mezzio\Container\WhoopsPageHandlerFactory::__invoke()
-
zendframework/zend-expressive#450 changes the interface inheritance of
Mezzio\Container\Exception\InvalidServiceExceptionto extendPsr\Container\ContainerExceptionInterfaceinstead ofInterop\Container\Exception\ContainerException.
- Nothing.
-
zendframework/zend-expressive#428 removes the following routing/dispatch methods from
Mezzio\Application:routeMiddleware(); this is now encapsulated inMezzio\Middleware\RouteMiddleware.dispatchMiddleware(); this is now encapsulated inMezzio\Middleware\DispatchMiddleware.
-
zendframework/zend-expressive#428 removes the various "final handler" implementations and related factories. Users should now use the "default delegates" as detailed in sections previous. Classes and methods removed include:
Mezzio\Application::getFinalHandler()Mezzio\TemplatedErrorHandlerMezzio\WhoopsErrorHandlerMezzio\Container\TemplatedErrorHandlerFactoryMezzio\Container\WhoopsErrorHandlerFactory
-
zendframework/zend-expressive#428 removes the
Mezzio\ErrorMiddlewarePipeclass, as laminas-stratigility 2.X no longer definesLaminas\Stratigility\ErrorMiddlewareInterfaceor has a concept of variant-signature error middleware. Use standard middleware to provide error handling now. -
zendframework/zend-expressive#428 removes the exception types
Mezzio\Container\Exception\InvalidArgumentException(useMezzio\Exception\InvalidArgumentExceptioninstead) andMezzio\Container\Exception\NotFoundException(which was never used internally).
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- zendframework/zend-expressive#447 fixes an
error in the
ApplicationFactorythat occurs when theconfigservice is anArrayObject. Prior to the fix,ArrayObjectconfigurations would cause a fatal error when injecting the pipeline and/or routes.
-
zendframework/zend-expressive#309 adds the ability to provide options with which to instantiate the
FinalHandlerinstance, via the configuration:[ 'final_handler' => [ 'options' => [ /* array of options */ ], ], -
zendframework/zend-expressive#373 adds interception of exceptions from the
ServerRequestFactoryfor invalid request information in order to return400responses. -
zendframework/zend-expressive#432 adds two new configuration flags for use with
Mezzio\Container\ApplicationFactory:mezzio.programmatic_pipelines: when enabled, the factory will ignore themiddleware_pipelineandroutesconfiguration, allowing you to wire these programmatically instead. We recommend creating these in the filesconfig/pipeline.phpandconfig/routes.php, respectively, and modifying yourpublic/index.phptorequirethese files in statements immediately preceding the call to$app->run().mezzio.raise_throwables: when enabled, this will be used to notify laminas-stratigility's internal dispatcher to no longer catch exceptions/throwables, and instead allow them to bubble out. This allows you to write custom middleware for handling errors.
-
zendframework/zend-expressive#429 adds
Mezzio\Application::getDefaultDelegate()as a forwards-compatibility measure for the upcoming version 2.0.0. Currently, it proxies togetFinalHandler(). -
zendframework/zend-expressive#435 adds support for the 2.X versions of mezzio-router and the various router implementations. This change also allows usage of mezzio-helpers 3.X.
-
zendframework/zend-expressive#429 updates the minimum supported laminas-stratigility version to 1.3.3.
-
zendframework/zend-expressive#396 updates the
Mezzio\Container\ApplicationFactoryto vary creation of theApplicationinstance based on two new configuration variables:-
mezzio.programmatic_pipelinewill cause the factory to skip injection of the middleware pipeline and routes from configuration. It is then up to the developer to do so, or use theApplicationAPI to pipe middleware and/or add routed middleware. -
mezzio.raise_throwableswill cause the factory to call the newraiseThrowables()method exposed byApplication(and inherited fromLaminas\Stratigility\MiddlewarePipe). Doing so will cause the application to raise anyThrowableorExceptioninstances caught, instead of catching them and dispatching them to (legacy) Stratigility error middleware.
-
- zendframework/zend-expressive#429 deprecates
the following methods and classes:
Mezzio\Application::pipeErrorHandler(); use theraise_throwablesflag and standard middleware to handle errors instead.Mezzio\Application::routeMiddleware(); this is extracted to a dedicated middleware class for 2.0.Mezzio\Application::dispatchMiddleware(); this is extracted to a dedicated middleware class for 2.0.Mezzio\Application::getFinalHandler()(this patch providesgetDefaultDelegate()as a forwards-compatibility measure)Mezzio\Container\Exception\InvalidArgumentException; this will be removed in 2.0.0, and places where it was used will instead throwMezzio\Exception\InvalidArgumentException.Mezzio\Container\Exception\NotFoundException; this exception is never thrown at this point.Mezzio\Container\TemplatedErrorHandlerFactoryMezzio\Container\WhoopsErrorHandlerFactoryMezzio\ErrorMiddlewarePipe; Stratigility 1.3 deprecates itsLaminas\Stratigility\ErrorMiddlewareInterface, and removes it in version 2.0. use theraise_throwablesflag and standard middleware to handle errors instead.Mezzio\TemplatedErrorHandler; the "final handler" concept is retired in Mezzio 2.0, and replaced with default delegates (classes implementingInterop\Http\ServerMiddleware\DelegateInterfacethat will be executed when the internal pipeline is exhausted, in order to guarantee a response). If you are using custom final handlers, you will need to rewrite them when adopting Mezzio 2.0.Mezzio\WhoopsErrorHandler
- zendframework/zend-expressive#406 removes the
RouteResultSubjectInterfaceimplementation fromMezzio\Application, per the deprecation prior to the 1.0 stable release.
- zendframework/zend-expressive#442 fixes how
the
WhoopsFactorydisables JSON output for whoops; previously, providing booleanfalsevalues for either of the configuration flagsjson_exceptions.show_traceorjson_exceptions.ajax_onlywould result in enabling the settings; these flags are now correctly evaluated by theWhoopsFactory.
- Nothing.
- Nothing.
- Nothing.
- zendframework/zend-expressive#420 fixes the
routeMiddleware()'s handling of 405 errors such that it now no longer emits deprecation notices when running under the Stratigility 1.3 series.
- Nothing.
- Nothing.
- Nothing.
- zendframework/zend-expressive#403 updates the
AppFactory::create()logic to raise exceptions in either of the following scenarios:- no container is specified, and the class
Laminas\ServiceManager\ServiceManageris not available. - no router is specified, and the class
Mezzio\Router\FastRouteRouteris not available.
- no container is specified, and the class
- zendframework/zend-expressive#405 fixes how
the
TemplatedErrorHandlerinjects templated content into the response. Previously, it wouldwrite()directly to the existing response body, which could lead to issues if previous middleware had written to the response (as the templated contents would append the previous contents). With this release, it now creates a newLaminas\Diactoros\Stream, writes to that, and returns a new response with that new stream, guaranteeing it only contains the new contents. - zendframework/zend-expressive#404 fixes the
swallowDeprecationNotices()handler such that it will not swallow a global handler once application execution completes.
- Nothing.
- Nothing.
- Nothing.
- zendframework/zend-expressive#402 fixes how
Application::__invoke()registers the error handler designed to swallow deprecation notices, as introduced in 1.0.3. It now checks to see if another error handler was previously registered, and, if so, creates a composite handler that will delegate to the previous for all other errors.
- Nothing.
- zendframework/zend-expressive#395 updates
Application::__invoke()to add an error handler to swallow deprecation notices due to triggering error middleware when using Stratigility 1.3+. Since error middleware is triggered whenever theraiseThrowablesflag is not enabled and an error or empty queue situation is encountered, handling it this way prevents any such errors from bubbling out of the application.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- zendframework/zend-expressive#393 updates
Application::run()to inject the request with anoriginalResponseattribute using the provided response as the value.
- Nothing.
- Nothing.
- zendframework/zend-expressive#393 fixes how
each of the
TemplatedErrorHandlerandWhoopsErrorHandleraccess the "original" request, URI, and/or response. Previously, these used Stratigility-specific methods; they now use request attributes, eliminating deprecation notices emitted in Stratigility 1.3+ versions.
- zendframework/zend-expressive#306 adds a cookbook recipe covering flash messages.
- zendframework/zend-expressive#384 adds support for Whoops version 2 releases, providing PHP 7 support for Whoops.
- Nothing.
- Nothing.
- zendframework/zend-expressive#391 fixes the
Application::run()implementation to prevent emission of deprecation notices when used with Stratigility 1.3.
Initial stable release.
- zendframework/zend-expressive#279 updates the documentation to provide automation for pushing to GitHub pages. As part of that work, documentation was re-organized, and a landing page provided. Documentation can now be found at: https://docs.mezzio.dev/mezzio/
- zendframework/zend-expressive#299 adds component-specific CSS to the documentation.
- zendframework/zend-expressive#295 adds support for handling PHP 7 engine exceptions in the templated and whoops final handlers.
- Nothing.
- Nothing.
- zendframework/zend-expressive#280 fixes
references to the
PlatesRendererin the error handling documentation. - zendframework/zend-expressive#284 fixes the reference to maximebf/php-debugbar in the debug bar documentation.
- zendframework/zend-expressive#285 updates the section on mtymek/blast-base-url in the "Using a Base Path" cookbook recipe to conform to its latest release.
- zendframework/zend-expressive#286 fixes the documentation of the Composer "serve" command to correct a typo.
- zendframework/zend-expressive#291 fixes the documentation links to the RC5 -> v1 migration guide in both the CHANGELOG as well as the error messages emitted, ensuring users can locate the correct documentation in order to upgrade.
- zendframework/zend-expressive#287 updates the
"standalone" quick start to reference calling
$app->pipeRoutingMiddleware()and$app->pipeDispatchMiddleware()per the changes in RC6. - zendframework/zend-expressive#293 adds
a
require 'vendor/autoload.php';line to the bootstrap script referenced in the laminas-servicemanager examples. - zendframework/zend-expressive#294 updates the namespace referenced in the modulear-layout documentation to provide a better separation between the module/package/whatever, and the application consuming it.
- zendframework/zend-expressive#298 fixes a typo in a URI generation example.
Seventh release candidate.
- zendframework/zend-expressive#277 adds a new
class,
Mezzio\ErrorMiddlewarePipe. It composes aLaminas\Stratigility\MiddlewarePipe, but implements the error middleware signature via its own__invoke()method.
- Nothing.
- Nothing.
- zendframework/zend-expressive#277 updates the
MarshalMiddlewareTraitto create and return anErrorMiddlewarePipewhen the$forErrorargument provided indicates error middleware is expected. This fix allows defining arrays of error middleware via configuration.
Sixth release candidate.
This release contains backwards compatibility breaks with previous release
candidates. All previous functionality should continue to work, but will
emit E_USER_DEPRECATED notices prompting you to update your application.
In particular:
- The routing middleware has been split into two separate middleware implementations, one for routing, another for dispatching. This eliminates the need for the route result observer system, as middleware can now be placed between routing and dispatching — an approach that provides for greater flexibility with regards to providing route-based functionality.
- As a result of the above,
Mezzio\Applicationno longer implementsMezzio\Router\RouteResultSubjectInterface, though it retains the methods associated (each emits a deprecation notice). - Configuration for
Mezzio\Container\ApplicationFactorywas modified to implement themiddleware_pipelineas a single queue, instead of segregating it betweenpre_routingandpost_routing. Each item in the queue follows the original middleware specification from those keys, with one addition: aprioritykey can be used to allow you to granularly shape the execution order of the middleware pipeline.
A migration guide was written to help developers migrate to RC6 from earlier versions.
- zendframework/zend-expressive#255 adds
documentation for the base path functionality provided by the
UrlHelperclass of mezzio-helpers. - zendframework/zend-expressive#227 adds a section on creating localized routes, and setting the application locale based on the matched route.
- zendframework/zend-expressive#244 adds
a recipe on using middleware to detect localized URIs (vs using a routing
parameter), setting the application locale based on the match detected,
and setting the
UrlHelperbase path with the same match. - zendframework/zend-expressive#260 adds a recipe on how to add debug toolbars to your Mezzio applications.
- zendframework/zend-expressive#261 adds a flow/architectural diagram to the "features" chapter.
- zendframework/zend-expressive#262 adds a recipe demonstrating creating classes that can intercept multiple routes.
- zendframework/zend-expressive#270 adds
new methods to
Mezzio\Application:dispatchMiddleware()is new middleware for dispatching the middleware matched by routing (this functionality was split fromrouteMiddleware()).routeResultObserverMiddleware()is new middleware for notifying route result observers, and exists only to aid migration functionality; it is marked deprecated!pipeDispatchMiddleware()will pipe the dispatch middleware to theApplicationinstance.pipeRouteResultObserverMiddleware()will pipe the route result observer middleware to theApplicationinstance; likerouteResultObserverMiddleware(), the method only exists for aiding migration, and is marked deprecated.
- zendframework/zend-expressive#270 adds
Mezzio\MarshalMiddlewareTrait, which is composed byMezzio\Application; it provides methods for marshaling middleware based on service names or arrays of services.
- zendframework/zend-expressive#270 deprecates
the following methods in
Mezzio\Application, all of which will be removed in version 1.1:attachRouteResultObserver()detachRouteResultObserver()notifyRouteResultObservers()pipeRouteResultObserverMiddleware()routeResultObserverMiddleware()
- zendframework/zend-expressive#270 removes the
Mezzio\Router\RouteResultSubjectInterfaceimplementation fromMezzio\Application. - zendframework/zend-expressive#270 eliminates
the
pre_routing/post_routingterminology from themiddleware_pipeline, in favor of individually specifiedpriorityvalues in middleware specifications.
- zendframework/zend-expressive#263 typo fixes in documentation
Fifth release candidate.
- zendframework/zend-expressive#233 adds a documentation page detailing projects using and tutorials written on Mezzio.
- zendframework/zend-expressive#238 adds a cookbook recipe detailing how to handle serving an Mezzio application from a subdirectory of your web root.
- zendframework/zend-expressive#239 adds a cookbook recipe detailing how to create modular Mezzio applications.
- zendframework/zend-expressive#243 adds a
chapter to the helpers section detailing the new
BodyParseMiddleware.
- Nothing.
- Nothing.
- zendframework/zend-expressive#234 fixes the
inheritance tree for
Mezzio\Exception\RuntimeExceptionto inherit fromRuntimeExceptionand notInvalidArgumentException. - zendframework/zend-expressive#237 updates the
Pimple documentation to recommend
xtreamwayz/pimple-container-interopinstead ofmouf/pimple-interop, as the latter consumed Pimple v1, instead of the current stable v3.
Fourth release candidate.
- zendframework/zend-expressive#217 adds a cookbook entry to the documentation detailing how to configure laminas-view helpers from other components, as well as how to add custom view helpers.
- Nothing.
- Nothing.
- zendframework/zend-expressive#219 updates the
"Hello World Using a Configuration-Driven Container" usage case to use
laminas-stdlib's
Glob::glob()instead of theglob()native function, to ensure the documented solution is portable across platforms. - zendframework/zend-expressive#223 updates the
documentation to refer to the
composer servecommand where relevant, and also details how to create the command for standalone users. - zendframework/zend-expressive#221 splits the various cookbook entries into separate files, so each is self-contained.
- zendframework/zend-expressive#224 adds opening
<?phptags to two configuration file examples, in order to prevent copy-paste errors.
Third release candidate.
- zendframework/zend-expressive#185 Support casting laminas-view models to arrays.
- zendframework/zend-expressive#192 adds support for specifying arrays of middleware both when routing and when creating pipeline middleware. This feature is opt-in and backwards compatible; simply specify an array value that does not resolve as a callable. Values in the array must be callables, service names resolving to callable middleware, or fully qualified class names that can be instantiated without arguments, and which result in invokable middleware.
- zendframework/zend-expressive#200,
zendframework/zend-expressive#206, and
zendframework/zend-expressive#211 add
functionality for observing computed
RouteResults.Mezzio\Applicationnow implementsMezzio\Router\RouteResultSubjectInterface, which allows attachingMezzio\RouteResultObserverInterfaceimplementations and notifying them of computedRouteResultinstances. The following methods are now available on theApplicationinstance:attachRouteResultObserver(Router\RouteResultObserverInterface $observer)detachRouteResultObserver(Router\RouteResultObserverInterface $observer)notifyRouteResultObservers(RouteResult $result);Applicationcalls this internally withinrouteMiddleware. This feature enables the ability to notify objects of the calculatedRouteResultwithout needing to inject middleware into the system.
- zendframework/zend-expressive#81 adds a cookbook entry for creating 404 handlers.
- zendframework/zend-expressive#210 adds a documentation section on the new mezzio/mezzio-helpers utilities.
- Nothing.
- zendframework/zend-expressive#204 removes the
RouterandTemplatecomponents, as they are now shipped with the following packages, respectively:- mezzio/mezzio-router
- mezzio/mezzio-template This package has been updated to depend on each of them.
- zendframework/zend-expressive#187 Inject the route result as an attribute
- zendframework/zend-expressive#197 updates the
Mezzio\Container\ApplicationFactoryto raise exceptions in cases where received configuration is unusable, instead of silently ignoring it. This is a small backwards compatibility break, but is done to eliminate difficult to identify issues due to bad configuration. - zendframework/zend-expressive#202 clarifies
that
RouterInterfaceimplements MUST throw aRuntimeExceptionifaddRoute()is called after eithermatch()orgenerateUri()have been called.
Second release candidate.
- Nothing.
- Nothing.
- Nothing.
- Updated branch aliases: dev-master => 1.0-dev, dev-develop => 1.1-dev.
- Point dev dependencies on sub-components to
~1.0-dev.
First release candidate.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- zendframework/zend-expressive#160 updates
EmitterStackto throw a component-specificInvalidArgumentExceptioninstead of the generic SPL version. - zendframework/zend-expressive#163 change the
documentation on wiring middleware factories to put them in the
dependenciessection ofroutes.global.php; this keeps the routing and middleware configuration in the same file.
- zendframework/zend-expressive#158 documents getting started via the installer + skeleton, and also documents "next steps" in terms of creating and wiring middleware when using the skeleton.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- zendframework/zend-expressive#156 updates how
the routing middleware pulls middleware from the container; in order to work
with laminas-servicemanager v3 and allow
has()queries to query abstract factories, a second, boolean argument is now passed.
- Nothing.
- Nothing.
- zendframework/zend-expressive#131 modifies the
repository to remove the concrete router and template renderer
implementations, along with any related factories; these are now in their own
packages. The classes removed include:
Mezzio\Container\Template\PlatesRendererFactoryMezzio\Container\Template\TwigRendererFactoryMezzio\Container\Template\LaminasViewRendererFactoryMezzio\Router\AuraRouterMezzio\Router\FastRouteRouterMezzio\Router\LaminasRouterMezzio\Template\PlatesRendererMezzio\Template\TwigRendererMezzio\Template\Twig\TwigExtensionMezzio\Template\LaminasViewRendererMezzio\Template\LaminasView\NamespacedPathStackResolverMezzio\Template\LaminasView\ServerUrlHelperMezzio\Template\LaminasView\UrlHelper
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- zendframework/zend-expressive#132 adds
Mezzio\Router\LaminasRouter, replacingMezzio\Router\LaminasRouter. - zendframework/zend-expressive#139 adds:
Mezzio\Template\TemplateRendererInterface, replacingMezzio\Template\TemplateInterface.Mezzio\Template\PlatesRenderer, replacingMezzio\Template\Plates.Mezzio\Template\TwigRenderer, replacingMezzio\Template\Twig.Mezzio\Template\LaminasViewRenderer, replacingMezzio\Template\LaminasView.
- zendframework/zend-expressive#143 adds
the method
addDefaultParam($templateName, $param, $value)toTemplateRendererInterface, allowing users to specify global and template-specific default parameters to use when rendering. To implement the feature, the patch also providesMezzio\Template\DefaultParamsTraitto simplify incorporating the feature in implementations. - zendframework/zend-expressive#133 adds a
stipulation to
Mezzio\Router\RouterInterfacethataddRoute()should aggregateRouteinstances only, and delay injection untilmatch()and/orgenerateUri()are called; all shipped routers now follow this. This allows manipulatingRouteinstances before callingmatch()orgenerateUri()— for instance, to inject options or a name. - zendframework/zend-expressive#133 re-instates
the
Route::setName()method, as the changes to lazy-inject routes means that setting names and options after adding them to the application now works again.
- Nothing.
- zendframework/zend-expressive#132 removes
Mezzio\Router\LaminasRouter, renaming it toMezzio\Router\LaminasRouter. - zendframework/zend-expressive#139 removes:
Mezzio\Template\TemplateInterface, renaming it toMezzio\Template\TemplateRendererInterface.Mezzio\Template\Plates, renaming it toMezzio\Template\PlatesRenderer.Mezzio\Template\Twig, renaming it toMezzio\Template\TwigRenderer.Mezzio\Template\LaminasView, renaming it toMezzio\Template\LaminasViewRenderer.
- Nothing.
- zendframework/zend-expressive#149 adds
verbiage to the
RouterInterface::generateUri()method, specifying that the returned URI MUST NOT be escaped. TheAuraRouterimplementation has been updated to internally usegenerateRaw()to follow this guideline, and retain parity with the other existing implementations.
- Nothing.
- Nothing.
- zendframework/zend-expressive#140 updates the
AuraRouter to use the request method from the request object, and inject that
under the
REQUEST_METHODserver parameter key before passing the server parameters for matching. This simplifies testing.
- zendframework/zend-expressive#128 adds
container factories for each supported template implementation:
Mezzio\Container\Template\PlatesFactoryMezzio\Container\Template\TwigFactoryMezzio\Container\Template\LaminasViewFactory
- zendframework/zend-expressive#128 adds
custom
urlandserverUrllaminas-view helper implementations, to allow integration with any router and with PSR-7 URI instances. The newly addedLaminasViewFactorywill inject these into theHelperPluginManagerby default.
- Nothing.
- Nothing.
- zendframework/zend-expressive#128 fixes an
expectation in the
WhoopsErrorHandlertests to ensure the tests can run successfully.
- Nothing.
- Nothing.
- Nothing.
- zendframework/zend-expressive#125 fixes the
WhoopsErrorHandlerto ensure it pushes the "pretty page handler" into the Whoops runtime.
- zendframework/zend-expressive#116 adds
Application::any()to complement the various HTTP-specific routing methods; it has the same signature asget(),post(),patch(), et al, but allows any HTTP method. - zendframework/zend-expressive#120 renames the
router classes for easier discoverability, to better reflect their usage, and
for better naming consistency.
AurabecomesAuraRouter,FastRoutebecomesFastRouteRouterandLaminasbecomesLaminasRouter.
- Nothing.
- zendframework/zend-expressive#120 removes the
classes
Mezzio\Router\Aura,Mezzio\Router\FastRoute, andMezzio\Router\Laminas, per the "Added" section above.
- Nothing.
- zendframework/zend-expressive#112 adds a chapter to the documentation on using Aura.Di (v3beta) with mezzio.
- Nothing.
- Nothing.
- zendframework/zend-expressive#118 fixes an
issue whereby route options specified via configuration were not being pushed
into generated
Routeinstances before being passed to the underlying router.
Initial tagged release.
- Everything.
- Nothing.
- Nothing.
- Nothing.