Extending EF Core codegen - API Limitation?
I'm currently building a package, EFCore.ModelExtras to let EF track database triggers and functions and migrate them like any other relation.
To achieve this, I've extended a bunch of EF's migration generation classes, like
Are there any ways around this without 2 package authors collaborating (e.g. a shared base type or intermediary API), or might I be missing some way to achieve inter-package compatibility with the existing EF Core API?
Would this be something worth writing a proposal around?
To achieve this, I've extended a bunch of EF's migration generation classes, like
ICSharpMigrationOperationGeneratorAre there any ways around this without 2 package authors collaborating (e.g. a shared base type or intermediary API), or might I be missing some way to achieve inter-package compatibility with the existing EF Core API?
Would this be something worth writing a proposal around?
