-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Labels
Platform(Default)domain/frameworkResponsible for the framework-level code includes core, administration, storefront, and frontendsResponsible for the framework-level code includes core, administration, storefront, and frontendspriority/highItems that we should do soon.Items that we should do soon.
Description
Shopware Version
6.6.10.13
Affected area / extension
Platform(Default)
Actual behaviour
When running the command on a Migration named e.g. Migration1770810936DoThings.php, the couldNotDetermineTimestamp MigrationException is thrown despite the name being correct.
This is a regression introduced with this change in RefreshMigrationCommand.php in 6.6.10.0: The converted regex format now includes the former delimiter # and the i flag at the end as literals. So if the migration file instead is named #Migration1770810936DoThings.php#i, the error is not thrown.
Expected behaviour
The error should not be thrown for the correct name.
How to reproduce
Create a migration with correct naming and run the command.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Platform(Default)domain/frameworkResponsible for the framework-level code includes core, administration, storefront, and frontendsResponsible for the framework-level code includes core, administration, storefront, and frontendspriority/highItems that we should do soon.Items that we should do soon.