fix: unfreeze DependencyFactory after command
#1528
+43
−22
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nikophil
changed the title
nikophil
force-pushed
the
feat/unfroze-dependencies-after-command
branch
from
e4ec2f3 to
458c7bf
Compare
nikophil
changed the title
DependencyFactory after command
nikophil
commented
Oct 4, 2025
| } | ||
|
|
||
| /** @throws SchemaDumpRequiresNoMigrations */ | ||
| public function execute( |
There was a problem hiding this comment.
not sure why this method was public
not sure this was made on purpose, but this change might be a small BC break in this case, if someone was using directly DumpSchemaCommand::execute() from outside. Should I handle this?
nikophil
force-pushed
the
feat/unfroze-dependencies-after-command
branch
from
458c7bf to
dd3e71d
Compare
nikophil
force-pushed
the
feat/unfroze-dependencies-after-command
branch
from
dd3e71d to
83a2951
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
When a migration command runs, the
DependencyFactoryis frozen, but never "unfrozen", so it cannot be run several times programmatically, like we would need in Foundry.I propose to unfreeze at the end of all commands, but I'd be also OK to only do it in
doctrine:migration:migrate