Consolidate overloads in MigrationsSqlGenerator #16654
Labels
breaking-change
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-cleanup
Milestone
I noticed that in MigrationsSqlGenerator we still have two overloads per operation, one receiving a
terminate
flag, and another which doesn't (and delegates to the first). Should we take this opportunity to clean this up, or is there some reason for this?/cc @bricelam
The text was updated successfully, but these errors were encountered: