Closed ericburcham closed 1 year ago
I concur this is likely a bit niave given the multi-db nature of EF. Consider adding an Application Intent like property to ContextConfiguration instead, extend DefaultConfiguration to make Read-Write the default. Then slotting a per DB strategy for ConnectionString build which can use the CC.
This pull request takes the opinion that when using a ReadonlyDbContext the ApplicationIntent on the connection string should be set to "readonly." This has the following effect:
If the project maintainers are of the opinion that the ApplicationIntent should be determined by the consumer of the Highway.Data.EntityFramework package, then this pull request should be rejected.