ed-fruty/laravel4-namespace-migrator

Package for Laravel 4, supporting using namespaces in migration classes

laravel4-namespace-migrator

Laravel 4 is not support namespaces in migration classes, but it is not a problem ;), _(*1)

Installation

1. Use Composer to install package into your project:, _(*2)

   ```bash composer require "ed-fruty/laravel4-namespace-migrator": "1.0.0", <sub>(*3)</sub>

2. Add the service provider in `app/config/app.php`:

  ```bash
  'Fruty\LaravelNamespaceMigrator\LaravelNamespaceMigratorServiceProvider',

1. Publish package configuration, <sub>(*4)</sub>

   ```bash php artisan config:publish ed-fruty/laravel4-namespace-migrator, <sub>(*5)</sub>

#Usage



Default migration namespaces searching


  When you call migrations like
```bash
php artisan migrate --path=app/Modules/Blog/Migrations

Migrator automatically searches classes with namespace App\Modules\Blog\Migrations in app/Modules/Blog/Migrations To change default values, edit configuration file app/config/packages/ed-fruty/laravel4-namespace-migrator/main.php block default, <sub>(*6)</sub>

Reserving namespaces for migration paths

For reserving namespace for some path, edit configuration file app/config/packages/ed-fruty/laravel4-namespace-migrator/main.php. Example:, <sub>(*7)</sub>

'reserved' => [
      base_path('app/modules/Blog/migrations') => 'Blog\\Migrations\\',
  ]

It means, when you call migrations like:, <sub>(*8)</sub>

php artisan migrate --path=app/modules/Blog/migrations

Migrator automatically searches classes with namespace Blog\Migrations in that directory., <sub>(*9)</sub>

Workbenches

For workbench packages Migrator automatically searches migrations by vendor/package name. When you call migrations like:, <sub>(*10)</sub>

php artisan migrate --bench=foo/bar

Migrator searches classes with namespace Foo\Bar\Migrations in workbench/foo/bar/src/migrations So if workbench namespace does not equal to vendor/package name you must register it in 'reserved' block like:, <sub>(*11)</sub>

base_path('workbench/foo/bar/src/migrations') => 'VendorNamespace\\PackageNamespace\\'

Without namespaces

Migrator always searches classes with namespace firstly and if class not found with namespace it trying to search class without namespace. For example basic usage:, <sub>(*12)</sub>

php artisan migrate, <sub>(*13)</sub>

By default configs, Migrator firstly searches migration classes with namespace App\database\migrations in app/database/migrations and if it does not exists, Migrator tries to load class without namespace from that catalog., <sub>(*14)</sub>