You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe the interface for ICoravelProDbContext is too restrictive in its implementation. The following interface of ICoravelProDbContext should not contain a set for the property.
A DbContext only requires a get method for any DbSet property. For example, the following is completely valid.
publicclassDatabase:DbContext,ICoravelProDbContext{protectedoverridevoidOnConfiguring(DbContextOptionsBuilderoptionsBuilder)=>optionsBuilder.UseSqlite("data source=app.db");// ReSharper disable once InconsistentNamingpublicDbSet<CoravelJobHistory>Coravel_JobHistory=>Set<CoravelJobHistory>();// ReSharper disable once InconsistentNamingpublicDbSet<CoravelScheduledJob>Coravel_ScheduledJobs=>Set<CoravelScheduledJob>();// ReSharper disable once InconsistentNamingpublicDbSet<CoravelScheduledJobHistory>Coravel_ScheduledJobHistory=>Set<CoravelScheduledJobHistory>();}
Yet, the inclusion of set forces users to implement a {get;set;}.
The text was updated successfully, but these errors were encountered:
I believe the interface for
ICoravelProDbContext
is too restrictive in its implementation. The following interface ofICoravelProDbContext
should not contain aset
for the property.A
DbContext
only requires aget
method for anyDbSet
property. For example, the following is completely valid.Yet, the inclusion of
set
forces users to implement a{get;set;}
.The text was updated successfully, but these errors were encountered: