2017 © Pedro Peláez
 

library zend-expressive-tooling

Migration and development tooling for Expressive

image

zendframework/zend-expressive-tooling

Migration and development tooling for Expressive

  • Tuesday, March 27, 2018
  • by zendframework
  • Repository
  • 21 Watchers
  • 24 Stars
  • 93,377 Installations
  • PHP
  • 21 Dependents
  • 2 Suggesters
  • 20 Forks
  • 6 Open issues
  • 28 Versions
  • 25 % Grown

The README.md

zend-expressive-tooling

Repository abandoned 2019-12-31

This repository has moved to mezzio/mezzio-tooling., (*1)

Build Status Coverage Status, (*2)

Migration and development tools for Expressive., (*3)

Installation

Install via composer:, (*4)

$ composer require --dev zendframework/zend-expressive-tooling

expressive Tool

  • vendor/bin/expressive: Entry point for all tooling. Currently exposes the following:, (*5)

    • action:create: Create an action class file; this is an alias for the handler:create command, listed below.
    • factory:create: Create a factory class file for the named class. The class file is created in the same directory as the class specified.
    • handler:create: Create a PSR-15 request handler class file. Also generates a factory for the generated class, and, if a template renderer is registered with the application container, generates a template and modifies the class to render it into a zend-diactoros HtmlResponse.
    • middleware:create: Create a PSR-15 middleware class file.
    • migrate:interop-middleware: Migrate interop middlewares and delegators to PSR-15 middlewares and request handlers.
    • migrate:middleware-to-request-handler: Migrate PSR-15 middlewares to request handlers.
    • module:create: Create and register a middleware module with the application.
    • module:deregister: Deregister a middleware module from the application.
    • module:register: Register a middleware module with the application.

Configurable command option values

If the --modules-path of your project is not under src, you can either provide the path via the --modules-path command-line option, or configure it within your application configuration. By adding the changed path to your application configuration, you can omit the need to use the --modules-path option during cli execution for the various module:* commands., (*6)

// In config/autoload/application.global.php:

<?php

declare(strict_types = 1);

use Zend\Expressive\Tooling\Module\CommandCommonOptions;

return [
    /* ... */
    CommandCommonOptions::class => [
        '--modules-path' => 'custom-directory',
    ],
];

The Versions

20/12 2016

0.2.0

0.2.0.0

Migration and development tooling for Expressive

  Sources   Download

BSD-3-Clause

The Requires

 

The Development Requires

middleware psr psr-7 http

08/12 2016

0.1.3

0.1.3.0

Migration and development tooling for Expressive

  Sources   Download

BSD-3-Clause

The Requires

 

The Development Requires

middleware psr psr-7 http

07/12 2016

0.1.2

0.1.2.0

Migration and development tooling for Expressive

  Sources   Download

BSD-3-Clause

The Requires

 

The Development Requires

middleware psr psr-7 http

06/12 2016

0.1.1

0.1.1.0

Migration and development tooling for Expressive

  Sources   Download

BSD-3-Clause

The Requires

 

The Development Requires

middleware psr psr-7 http

06/12 2016

0.1.0

0.1.0.0

Migration and development tooling for Expressive

  Sources   Download

BSD-3-Clause

The Requires

 

The Development Requires

middleware psr psr-7 http