Allow namespaced migration files

[dereuromark]

I wonder if we could use cakephp/phinx#1820 to namespace our migration classes
They are the only code I still have to exclude from sniffers so far:

FOUND 2 ERRORS AFFECTING 1 LINE
----------------------------------------------------------------------------------------------------------------------------------------
 6 | ERROR | Class name "MigrationLanguages" doesn't match filename, expected "20201014000218_MigrationLanguages"
 6 | ERROR | Each class must be in a namespace of at least one level (a top-level vendor name)

With the namespace way it would also probably be a bit cleaner and less conflicting regarding the names.

Right now I always prefix them with Migration to avoid naming clashes/collisions with existing top level classes.

[dereuromark]

The CS issue is "hacked" for now with cakephp/cakephp-codesniffer#320

We should still looking into a phinx solution that allows namespace migration class names, though.
According to https://github.com/cakephp/phinx/blob/master/docs/en/namespaces.rst#psr-4-compliance this should already be possible, maybe sth for Cake 4.2+?

[dereuromark]

laravel also spaces the timestamp datetime for readability:

2024_07_15_203230_CreateProductsTable

We could do sth similar when we refactor this into class namespaced or alike.

[markstory]

Revisiting the filenames and namespacing of migrations are both things I'd like to follow up on once phinx is removed. Doing it before that time will create compatibility issues.

[LordSimal]

I'd rather use anonymous classes and no namespaces (like e.g. Laravel does).
We can for sure make CS work with that as well.

[dereuromark]

I agree that if we move to anonm. class and no namespace, we could just as well move them into

resources/

folder instead of config/

We have to find a way to make it CS/PHPStan compatible, though without having to silence a lot.

[umer936]

2024_07_15_203230_

I like this.