Expressive zend-view integration 1.3.0

Added

• #23 adds the ability to disable layouts either globally or when rendering. Disable globally by setting the default layout parameter to boolean false:

  $renderer->addDefaultParam(TemplateRendererInterface::TEMPLATE_ALL, 'layout', false);

  Or do so when rendering, by passing the template variable layout with a boolean false value:

  $renderer->render($templateName, [
      'layout' => false,
      // other template variables
  ]);

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• Nothing.

Expressive zend-view integration 1.2.1

Added

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• #33 fixes the signature of the UrlHelper to make the default value of $fragmentIdentifer a null instead of ''; this fixes an issue whereby missing fragments led to exceptions thrown by zend-expressive-helpers.

Expressive zend-view integration 1.2.0

Added

• #30 adds support for zend-expressive-router 2.0.

• #30 adds support for zend-expressive-helpers 2.2 and 3.0.

• #30 adds new arguments to the url() helper:

  echo $this->url(
      $routeName,   // (optional) string route for which to generate URI; uses matched when absent
      $routeParams, // (optional) array route parameter substitutions; uses matched when absent
      $queryParams, // (optional) array query string arguments to include
      $fragment,    // (optional) string URI fragment to include
      $options,     // (optional) array of router options. The key `router` can
                    //     contain options to pass to the router; the key
                    //     `reuse_result_params` can be used to disable re-use of
                    //     matched routing parameters.
  );

  If using zend-expressive-router versions prior to 2.0 and/or zend-expressive-helpers versions prior to 3.0, arguments after $routeParams will be ignored.

Changed

• #26 updated the zend-view dependency to 2.8.1+.

Deprecated

• Nothing.

Removed

• #26 removes the dependencies for the zend-i18n and zend-filter packages, as they are no longer required by the minimum version of zend-view supported.

  If you depended on features of these, you may need to re-add them to your application:

  $ composer require zendframework/zend-filter zendframework/zend-i18n

• This release removes support for PHP 5.5.

Fixed

• Nothing.

Expressive zend-view integration 1.1.0

Added

• #22 adds support for the zend-eventmanager and zend-servicemanager v3 releases.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• Nothing.

Expressive zend-view integration 1.0.1

The confusion is that both routed middleware and pipeline middleware define paths. For routed middleware, this is a routing specification — which can be a literal, but which often typically some sort of matching rules. For pipeline middleware, this is a literal path prefix only, and that prefix is stripped when the request is passed to the middleware it matches.