Add EntityTypeConfiguration<TEntity>

[rowanmiller]

Resolves #2805

[ajcvickers]

Why is this not an interface?

[rowanmiller]

Because the thought didn't even cross my mind... I was just doing it like we did in EF6 (eyeroll from @anpete 😁). I'll swap it to an interface.

[ajcvickers]

[anpete]

May want to create a separate bug for auto-discovery of these, which is mentioned in the original bug.

[anpete]

Are we OK with only having a generic version?

[rowanmiller]

I don't know that we want to auto-scan for these but I think an AddFromAssembly like we had in EF6 is an ok idea.

I played with having a non-generic one too - mostly so that I could have an ApplyConfiguration() method (which is super messy with just the generic version). I'm happy to add it if we think it's helpful. I decided not to because you end up with public stuff on the generic version that is distracting (public Type EntityType { get;} etc.)... but happy to add it back.

[ErikEJ]

@sjh37 !!

[sjh37]

A nice improvement. I'll make sure to add this to the EF core reverse generator.

[ErikEJ]

@sjh37 Yes, it should allow you to split the files in a similar way to how you do it now

[rowanmiller]

Decided in design meeting to just keep the generic version. Updated PR to use interface rather than abstract base class.

[anhphan]

Not sure keeping Generic style is a good idea, currently I have a self implement of mapping and I have something like this for registration:

        protected override void OnModelCreating(ModelBuilder modelBuilder)
        {
            var collections = ServiceProvider.GetServices<IModelBuilder>();
            foreach (var callback in collections)
            {
                callback.OnModelCreating(modelBuilder);
            }
        }

For auto scan, I used ApplicationParts to registry Mapping class to DI.

[Diaskhan]

After on cofiguring we could access to dbset of dbcontext?
How usually manipulate with dynamically loading poco objects ?