Lets several schema types share one dotnet type - the case for EF Core shared-type entities, where tables known only at runtime are property bags (Dictionary<string, object>) with no class per table. Each field names its schema type with Returns("Type"), and the schema now takes it from the field.

var author = schema.AddType<Dictionary<string, object>>("Author", null);
var priority = schema.AddType<Dictionary<string, object>>("Priority", null);
priority.AddField("score", p => EF.Property<int>(p, "score"), null);
priority.AddField("author", p => EF.Property<Dictionary<string, object>>(p, "author"), null).Returns("Author");
schema.Query().AddField("priorities", db => db.Set<Dictionary<string, object>>("priorities"), null)
    .Returns("Priority").UseFilter().UseSort(useSchemaFields: true);

What was broken, and the fix

ExpressionUtil.BuildEntityQueryExpression gains an overload taking the schema type; the existing signature is kept, so this is binary compatible.

One behaviour change, called out in the changelog: ReturnType.TypeDotnet of a field that used Returns("Type") is now the field's own dotnet type rather than the named type's. Code reading it as the element type should use GetEnumerableOrArrayType().

Version

main was at 6.3.1, which has not been released (NuGet's latest is 6.3.0). This adds to the API, so it bumps to 6.4.0, and the unreleased 6.3.1 changelog section becomes 6.4.0's.

Tests

• SharedDotnetTypeTests (in memory): selection, both directions of a relation, filter (direct, through a reference, through any), sort, and ReturnType after Returns.
• SharedTypeEntityTests (EF Core over SQLite, which throws if anything does not translate): the same over real shared-type entities.
• Without the library changes, 12 of the 13 new tests fail (one-to-many already worked); the whole suite passes on net8.0, net9.0 and net10.0.

Found while building dynamic per-app schemas for Tredle, where each app's tables come from its own migrations.

Also noticed: .config/dotnet-tools.json names the CSharpier command dotnet-csharpier, but CSharpier 1.0.0 ships it as csharpier, so dotnet tool restore fails. Not changed here.

🤖 Generated with Claude Code