Closed nicolas-grekas closed 1 year ago
This is something we figured out in Symfony: when there is no mapping info available, it doesn't mean there is no migration to generate. This happens when there are schema listeners that integrate with migrations, as is the case for those: https://github.com/symfony/symfony/tree/6.2/src/Symfony/Bridge/Doctrine/SchemaListener
Right now, one has to have entities before they can generate migrations, but those schema are entity-less.
Removing this check does the job.
(phpstan failures are unrelated)
I fixed the PHPStan failures in https://github.com/doctrine/migrations/pull/1286
Can you please rebase?
All green in a minute.
This is something we figured out in Symfony: when there is no mapping info available, it doesn't mean there is no migration to generate. This happens when there are schema listeners that integrate with migrations, as is the case for those: https://github.com/symfony/symfony/tree/6.2/src/Symfony/Bridge/Doctrine/SchemaListener
Right now, one has to have entities before they can generate migrations, but those schema are entity-less.
Removing this check does the job.