I’ve been reading Iñaki’s comment about improving the extensibility of Migrations as well as reviewing his pull request. Even if I agree that it improves Migration’s extensibility, I’m not so sure it’s the way developers should go about it. If we apply it, for each operation I’ll need to subclass SqlServerMigrationSqlGenerator to add a custom Generate, because this responsibility can’t be independent, and leave SqlServerMigrationSqlGenerator as a container of “parts that can Generate”? In my opinion it would be a better approach to have a chain of responsibility, so the developer wanting to add a new operation can define both the operation and it’s Generate and inject them in SqlServerMigrationSqlGenerator. What do you think?
Thanks in advance
Unai