Question: Why do we need to register migration commands as services with a factory?

[thexpand]

I tested the migrations functionality with and without registering the migrations commands inside the factories. It works even without registering them, when I try to call php vendor/bin/doctrine-migrations xxxxx, where xxxxx is the command. So, why do we need to register the commands as services?

[asgrim]

It's been a while since I looked at that; if we can verify the service configuration really isn't needed, then it should be removed from docs 👍

[thexpand]

I tried to search for a code that uses these services in the whole project, but I can't find one. How can we verify this for sure?

[asgrim]

@thexpand the example is just "how you might configure it in your project". If you don't need/want to register your commands as services, then that is fine, just skip that step. Perhaps clarification on the docs would help :)

[asgrim]

I tried to search for a code that uses these services in the whole project, but I can't find one. How can we verify this for sure?

Oh and you won't find any services used in this project, if that's what you mean? This library does not consume services, it only provides factories so you can wire them into your container.

[thexpand]

@asgrim Ah, I understand now. But why would you need them as services in the first place? Can you give me an example of a possible scenario for this? The only possible use case I can think of is to execute a migration command in another symfony-console custom command that I have in the application.

[asgrim]

Generally when using symfony/console, using a container allows you to configure (manually, I don't think it's out the box, can't remember) lazy-loading services meaning unused dependencies aren't initiated :)