CoreEx.EntityFrameworkCore 4.0.0-preview-1

CoreEx.EntityFrameworkCore

Provides the Entity Framework Core integration layer: EfDb<TDbContext> as the CoreEx-EF bridge, EfDbModel<TModel> and EfDbMappedModel<TValue, TModel, TMapper> for typed CRUD + query operations, EfDbExtensions for paged IQueryable<T> mapping helpers, EfDbInvoker for OpenTelemetry tracing, and EF ValueConverter bridges for CoreEx converter types.

Overview

CoreEx.EntityFrameworkCore wraps EF Core's DbContext with the CoreEx data conventions: IUnitOfWork transaction management, ETag/concurrency-token checking, multi-tenancy filtering, logical-delete filtering, change-log stamping, PagingArgs paging, QueryArgsConfig dynamic filter/orderby, and Result<T> pipeline integration.

The central type is EfDb<TDbContext>, which holds the DbContext, bridges its IDatabase (for transaction sharing with raw SQL), and exposes Model<TModel>() as the entry point for all strongly-typed CRUD. EfDbModel<TModel> provides GetAsync, CreateAsync, UpdateAsync, DeleteAsync, and Query — each applying the full CoreEx cross-cutting pipeline. EfDbMappedModel<TValue, TModel, TMapper> adds a IBiDirectionMapper layer for use cases where the EF model type differs from the domain entity type.

EfDbExtensions provides IQueryable<T> extension methods for mapping, paging, and ItemsResult<T> collection building, enabling consistent paged-list patterns across all EF-backed repositories without boilerplate.

Key capabilities

• 🔗 EF + IDatabase bridge: EfDb<TDbContext> synchronizes EF Core's transaction with the underlying IDatabase.CurrentTransaction, so raw SQL commands and EF operations participate in the same ADO.NET transaction.
• 📖 Typed CRUD: EfDbModel<TModel> provides GetAsync, CreateAsync, UpdateAsync, DeleteAsync with automatic ETag/concurrency-token validation, tenant isolation, logical-delete filtering, and change-log stamping.
• 🔁 Mapped CRUD: EfDbMappedModel<TValue, TModel, TMapper> layers a IBiDirectionMapper<TValue, TModel> over EfDbModel<TModel>, mapping between the domain entity type and the EF model type transparently for all CRUD operations.
• 🔍 Query with dynamic filter/orderby: EfDbModel<TModel>.Query(args?) returns a fluent EfDbQuery<TModel> that applies QueryArgsConfig filter and orderby, tenant and logical-delete predicates, and paging.
• 📄 Paged IQueryable extensions: EfDbExtensions.ToMappedItemsResultAsync, ToItemsResultAsync, ToMappedCollectionAsync convert an IQueryable<TSource> to paged ItemsResult<T> or collections with a mapper function or IMapper<T>.
• 🏷️ ETag / concurrency token: EfDbArgs.CheckETag compares the incoming ETag against the current entity's concurrency token before update/delete, throwing ConcurrencyException on mismatch.
• 🔒 Multi-tenancy filtering: EfDbModel automatically adds TenantId == executionContext.TenantId predicates for entities implementing IReadOnlyTenantId.
• 🗑️ Logical delete: Entities implementing IReadOnlyLogicallyDeleted are soft-deleted (IsDeleted = true) on DeleteAsync rather than physically removed, and filtered out of GetAsync / Query.
• 🔌 ValueConverter bridge: ValueConverterBridge<TModel, TProvider> and JsonElementStringEfConverter allow CoreEx IConverter<T, U> implementations to be used directly as EF Core ValueConverter instances in OnModelCreating.
• 📡 OpenTelemetry: EfDbInvoker wraps every EfDb operation with an Activity span tagged with operation type, model type, and result.

Key types

Namespaces

Related Namespaces

• CoreEx.Data - IUnitOfWork, DataResult, QueryArgsConfig; EF unit-of-work is typically composed using EfDb with an outbox publisher.
• CoreEx.Database - IDatabase is bridged into EfDb<TDbContext> for transaction sharing and raw SQL fallback; IDatabaseUnitOfWork can wrap EfDb.
• CoreEx.Mapping - IBiDirectionMapper<TValue, TModel> is the mapper contract used by EfDbMappedModel; Mapper.MapStandardFrom handles standard entity-contract properties.
• CoreEx.Invokers - EfDbInvoker extends InvokerBase<IEfDb> using the standard OpenTelemetry tracing and logging pipeline.

AI Usage Guide

An AGENTS.md file is included with this package. AI coding assistants (GitHub Copilot, Claude, Cursor, etc.) that support workspace-injected package documentation will automatically surface concise usage guidance, code examples, and Do Not rules for this package without requiring a local CoreEx checkout.