Csag.Blueprint.Application 0.5.0

Csag.Blueprint.Application

Overview

This package provides application-layer abstractions for CSAG Blueprint-based applications: service interfaces, claim type constants, tenant context management, and a full table view query system. It sits between Domain and Infrastructure, defining contracts that infrastructure and app layers implement.

Claims

• IdentityClaimTypes: Static constants for identity claim types used across the application (TenantId, Permission, PreferredLanguage). They are stored in the authentication ticket so they are available on every request without a database lookup.
• ServiceAccountClaimTypes: The claim names a service-account bearer token and its principal carry — Subject (sub, the client id), Name (name), Type (type, always ServiceAccountType) and SessionId (sid, the opaque session reference). The bearer scheme does not map inbound claims, so these raw names are what the principal carries.

Tenant Context

• TenantContext: Ambient AsyncLocal-backed storage for the current tenant ID. Set by middleware, read by query filters, save interceptors, and application code via SetTenant(), Current, and Clear().

Service Abstractions

All service contracts are defined as interfaces for dependency injection and testability.

Table View System

A generic, permission-aware system for server-side filtered, sorted, and paginated data grids. Application code defines views using a fluent API; infrastructure executes them against EF Core.

Defining a table view

Subclass TableViewDefinition<TEntity, TDto> and configure columns in the constructor:

public sealed class UserTableViewDefinition : TableViewDefinition<UserEntity, UserDto>
{
    public UserTableViewDefinition()
    {
        Column(dto => dto.Name)
            .Filterable(TableViewFilterOperator.Contains)
            .Sortable();

        Column(dto => dto.Email)
            .Filterable(TableViewFilterOperator.Contains)
            .Sortable();

        ComputedColumn("FullName", entity => entity.FirstName + " " + entity.LastName, dto => dto.FullName)
            .Sortable();
    }
}

Key components

Filter operators

Allowed values and labels

Enum and In filters offer a column's AllowedValues, each a TableViewAllowedValue serialized as { "value": "...", "label": "..." }. Filters match on value; label is display text.

An enum column derives one entry per member: the member name as the value, the humanized name as the label (CreditCard → "Credit card", SMSCode → "SMS code"), and Enums.{EnumTypeName}.{MemberName} as the label's translation key. The key is optional: add it to the translation catalog to translate the label, otherwise the humanized label is served.

Column(dto => dto.PaymentMethod)
    .Filterable(TableViewFilterOperator.Enum)
    .WithValueLabelKeyPrefix("Payments.Methods"); // keys "Payments.Methods.{Value}", warned when missing

Column(dto => dto.Size)
    .Filterable(TableViewFilterOperator.In)
    .WithAllowedValues([new("S", "Small"), new("L", "Large") { LabelKey = "Sizes.Large" }]);

WithAllowedValues(IEnumerable<string>) and Filterable(operator, allowedValues) take plain strings, served with the string itself as the label. Excel exports write matching cells as their label.

Request / Result models

• TableViewDataRequest: Incoming request with filters, sort, page, and page size.
• TableViewQueryRequest<TEntity, TDto>: Internal request that pairs a base IQueryable with a ITableViewDefinition and pagination parameters.
• TableViewDataResult<TDto>: Response with column metadata, data, total count, and computed page info.
• TableViewPreferencesModel: Serializable user preferences for a specific view.