Why is class 'Elsa.EntityFrameworkCore.Modules.Management.Configurations' marked as internal

[englebertnicolas]

Hello, why is class 'Elsa.EntityFrameworkCore.Modules.Management.Configurations' marked as internal ?
(but class 'Elsa.EntityFrameworkCore.Modules.Runtime.Configurations' is public).
Elsa 3.3.0.

I would like to build a unified DbContext that includes Management entities, Runtime entities and my own entities, like this:

public class MyDbContext : DbContext {
    public DbSet<WorkflowDefinition> WorkflowDefinitions { get; set; } = default!;
    public DbSet<WorkflowInstance> WorkflowInstances { get; set; } = default!;
    public DbSet<StoredBookmark> Bookmarks { get; set; } = default!;
    ...

    protected override void OnModelCreating(ModelBuilder modelBuilder) {
        base.OnModelCreating(modelBuilder);
        modelBuilder.HasDefaultSchema(Elsa.EntityFrameworkCore.ElsaDbContextBase.ElsaSchema);

        // Apply configuration for Runtime.Entities
        var runtimeConfig = new Elsa.EntityFrameworkCore.Modules.Runtime.Configurations();
        modelBuilder.ApplyConfiguration<StoredBookmark>(runtimeConfig);

        // Apply configuration for Management.Entities
        var managementConfig = new Elsa.EntityFrameworkCore.Modules.Management.Configurations(); //DOES NOT COMPILE BECAUSE IS INTERNAL
        modelBuilder.ApplyConfiguration<WorkflowDefinition>(managementConfig);
        modelBuilder.ApplyConfiguration<WorkflowInstance>(managementConfig);
        ...
    }
}

[sfmskywalker]

In Elsa 3.3.0, Elsa.EntityFrameworkCore.Modules.Management.Configurations is intentionally internal: it is an implementation detail used by ManagementElsaDbContext, not a supported composition API. The runtime Configurations type being public is inconsistent with that boundary and should not be taken as a guarantee that either configuration class is stable for external combined contexts.

Elsa's EF Core persistence features are built around separate ManagementElsaDbContext and RuntimeElsaDbContext factories. They may share the same database/schema, but a single unified application DbContext is not a supported integration point in 3.3.0.

If a single context is a hard requirement, you would need to own the entity mappings and migrations for the Elsa version you target, including its shadow/serialized properties and indexes; copying an internal configuration couples that context to Elsa internals. Please open a focused feature request if a public combined-context contract would be valuable.

Relevant 3.3.0 source: https://github.com/elsa-workflows/elsa-core/blob/3.3.0/src/modules/Elsa.EntityFrameworkCore/Modules/Management/DbContext.cs and https://github.com/elsa-workflows/elsa-core/blob/3.3.0/src/modules/Elsa.EntityFrameworkCore/Modules/Management/Configurations.cs