Fluent API: support like EF IEntityTypeConfiguration for seperate domain entity

[a-patel]

I do not want to change the domain entities using a decorator.
I want something like this,

            //dynamically load all configuration
            //System.Type configType = typeof(LanguageMap);   //any of your configuration classes here

            var typesToRegister = Assembly.GetExecutingAssembly().GetTypes()
            .Where(type => !string.IsNullOrEmpty(type.Namespace))
            .Where(type => type.BaseType != null && type.BaseType.IsGenericType &&
                type.BaseType.GetGenericTypeDefinition() == typeof(EntityTypeConfiguration<>));
            foreach (var type in typesToRegister)
            {
                dynamic configurationInstance = Activator.CreateInstance(type);
                modelBuilder.ApplyConfiguration(configurationInstance);
            }
            //...or do it manually below. For example,
            //modelBuilder.Configurations.Add(new LanguageMap());

[a-patel]

FYI.
another approach,
https://github.com/tflanitzer/Sieve/blob/explicit-properties/SieveTests/Controllers/PostsController.cs

[Biarity]

Fluent API is already supported: #4 (comment)

[a-patel]

I know Fluent API is supported already.
I want to load/register Fluent API for particular domain dynamically.
e.g. find base class or interface implementation in assemblies.

[a-patel]

I have also looked into the pull request,
https://github.com/tflanitzer/Sieve/tree/explicit-properties

I want similar that kind of approach, but not in controller.

[a-patel]

public partial class BlogPostMap : IEntityTypeConfiguration<BlogPost>
    {
        public override void Configure(EntityTypeBuilder<BlogPost> builder)
        {
            base.Configure(builder);
            builder.ToTable("BlogPost");
            builder.HasKey(bp => bp.Id);
            builder.Property(bp => bp.Title).IsRequired();
            builder.Property(bp => bp.Body).IsRequired().HasMaxLength(400);
        }
    }

I am asking for such functionality.
So one can find the IEntityTypeConfiguration implementation in other assembly and load them dynamically.

[a-patel]

This is just suggestion,
#Good to Have feature.

[Biarity]

What if you create multiple subclasses with different fluent APIs then use something like DI to choose the one you want to be used?

[a-patel]

It will be great if you can give me an example code.
Thank you in advance.

[a-patel]

any update?

[Biarity]

Sorr for the delay - I meant creating multiple subclasses of SieveProcessor (instead of just the 1 as you'd do for the fluent API normally). Then you'd be able to manually choose which implementation to use.

[a-patel]

then how to register 'SieveProcessor'?
It will be very very helpful, if you can give an example.

[a-patel]

Basically I want new change in core functionality,
I need to find all classes which implemented one base class/interface (i.e. IEntityTypeConfiguration in EF API) in particular assembly(es),
and register such classes in SieveProcessor.

Hope you understand my requirement.

[a-patel]

please do the needful.
thank you

[Biarity]

Creating multiple subclasses looks like:

public class ApplicationSieveProcessorOne : SieveProcessor
{
    public ApplicationSieveProcessor(
        IOptions<SieveOptions> options, 
        ISieveCustomSortMethods customSortMethods, 
        ISieveCustomFilterMethods customFilterMethods) 
        : base(options, customSortMethods, customFilterMethods)
    {
    }

    protected override SievePropertyMapper MapProperties(SievePropertyMapper mapper)
    {
      //mapper details from issue #4
    }
}

and another one

public class ApplicationSieveProcessorTwo : SieveProcessor
{
    public ApplicationSieveProcessor(
        IOptions<SieveOptions> options, 
        ISieveCustomSortMethods customSortMethods, 
        ISieveCustomFilterMethods customFilterMethods) 
        : base(options, customSortMethods, customFilterMethods)
    {
    }

    protected override SievePropertyMapper MapProperties(SievePropertyMapper mapper)
    {
      //DIFFERENT mapper details from issue #4
    }
}

Now just use whichever class you want. I'm not really sure why this wouldn't work for ya. Are you using it with ASP.NET Core and the default DI? If so, you can easily inject whichever class you want in Startup.cs.

[Dzivo]

I dont aggree with you @Biarity this is very inefective.

EF Core enables us to use builder from our models without any other setup you just need to implement interface. This should't be that hard to implement since you already have SieveProcessor.

If you would like i can make a pull request but only if you are interested in such a feature :)

[Dzivo]

For now i use something like this

public class MyEntity : ISieveConfiguration
{
  public string Name { get; set; }

  public void ConfigureSieve(SievePropertyMapper mapper)
  {
    mapper.Property<Regatta>(p => p.Name)
      .CanFilter();
  }
}

public interface ISieveConfiguration
{
  public void ConfigureSieve(SievePropertyMapper mapper);
}

public class CustomSieveProcessor : SieveProcessor
{
    public CustomSieveProcessor(
        IOptions<SieveOptions> options)
        : base(options)
    {
    }

    protected override SievePropertyMapper MapProperties(SievePropertyMapper mapper)
    {
      Assembly
        .GetExecutingAssembly()
        .GetTypes()
        .Where(m => m.GetInterfaces().Any(i => i == typeof(ISieveConfiguration)))
        .ToList()
        .ForEach(m =>
        {
          var instance = Activator.CreateInstance(m);
          m.GetMethod("ConfigureSieve").Invoke(m, new object[] { mapper });
        });

      return mapper;
    }
}