Move migrations under the Phinx\Migration namespace

[robmorgan]

In order to stop polluting the global namespace we will move migration classes under the Phinx\Migration namespace. This also conforms to PSR-2.

[robmorgan]

Need to do a much better job of this.

Tasks

• Fix Manager Classes to work with Namespaces
• Fix Unit Tests
• Find a solution for existing projects with migrations not under a namespace

[ferodss]

Maybe in 1.0 tag?! We broken compatibility in 1.0 release, no need much code to still work....

[robmorgan]

@felipedjinn yes I think it will need to wait until 1.0 or 1.5. will break too much BC.

[cyrusboadway]

@robmorgan In my mind, the ideal would allow arbitrary namespaces, either specified in the config and imported into the default template, or defined on a migration-by-migration basis, so that we can arrange the migrations in whichever directory/namespace structure makes sense for our application.

[evought]

If you go as @cyrusboadway suggests and allow a namespace to be specified in the config, then that will allow each project to put the migrations in their own vendor namespace and still preserve existing projects using the global namespace. New projects could default to Phinx\Migration . It would then become a backwards-compatible change.

Basically:

• If the configuration value is defined, put/find migrations in the specified namespace.
• The the configuration value does not exist, use the global namespace (current, backwards-compatible behavior).
• When a new project is created (or transitions to phinx), have "phinx init" set the configuration value to Phinx\Migration in the generated phinx.yml. The user will have the opportunity to edit the value if desired.

[t1gor]

That's exactly what I'm looking for. Any update on the issue?

[arogachev]

I switched to Phinx from native framework migrations (I'm using Yii2) just to give it a try and see it in action. But this is for now is one of the biggest disadvantages for me. Any update on this?

I want namespace to be console\migrations\phinx. Maybe some workarounds exist? If I try to specify namespace, during migrate / rollback "No class found" expection is thrown.