Cirreum.Runtime.Client 1.0.27

Cirreum.Runtime.Client

Comprehensive client-side runtime infrastructure for Blazor WebAssembly applications

Overview

Cirreum.Runtime.Client provides a complete foundation for building robust Blazor WebAssembly applications with built-in support for authentication, state management, theming, user presence, and component infrastructure.

Features

• Authentication & Security

  • Flexible authentication with claims processing
  • No-auth fallback for development scenarios
  • Post-processing hooks for user enrichment

• State Management

  • Multiple state scopes: Memory, Session, Local Storage, and Container
  • ViewModels with property change tracking
  • Persistent and transient state patterns

• Component Library

  • Session activity monitoring with expiration dialogs
  • User presence badges and indicators
  • Profile cards and management
  • Theme switcher with dark/light mode support
  • Validation components with FluentValidation integration

• Developer Experience

  • Comprehensive base classes for pages and components
  • Startup task infrastructure
  • JavaScript interop module system
  • SCSS compilation and theming support

Installation

dotnet add package Cirreum.Runtime.Client

Quick Start

using Microsoft.AspNetCore.Components.WebAssembly.Hosting;
using Cirreum.Runtime;

var builder = WebAssemblyHostBuilder.CreateDefault(args);

// Configure Cirreum Runtime Client
builder.Services.AddCirreumRuntimeClient(options =>
{
    options.EnableAuthentication = true;
    options.EnablePresenceMonitoring = true;
    options.EnableThemeManagement = true;
});

await builder.Build().RunAsync();

Usage Examples

State Management

// Using a memory state component
@inherits MemoryStateComponent<MyState>

@code {
    protected override void OnInitialized()
    {
        State.PropertyChanged += (s, e) => StateHasChanged();
    }
}

User Presence

<UserPresenceBadge UserId="@userId" Size="PresenceBadgeSize.Large" />

Theme Management

<ThemeSelector />

Session Monitoring

<SessionActivityMonitor WarningMinutes="5" />

Architecture

The library is organized into several key namespaces:

• Cirreum.Runtime.Authentication - Authentication infrastructure and claims processing
• Cirreum.Runtime.Components - Reusable Blazor components
• Cirreum.Runtime.Components.ViewModels - State management and view model patterns
• Cirreum.Runtime.Security - Security providers and user management
• Cirreum.Runtime.StartupTasks - Application initialization tasks

Demo Application

The repository includes a comprehensive demo application showcasing all features:

cd samples/Cirreum.Demo.Client
dotnet run

The demo includes examples of:

• Navigation layouts with theming
• User presence indicators
• State management patterns
• Time zone and internationalization features
• Weather data with session state
• Notification system

Contribution Guidelines

1. Be conservative with new abstractions
   The API surface must remain stable and meaningful.

2. Limit dependency expansion
   Only add foundational, version-stable dependencies.

3. Favor additive, non-breaking changes
   Breaking changes ripple through the entire ecosystem.

4. Include thorough unit tests
   All primitives and patterns should be independently testable.

5. Document architectural decisions
   Context and reasoning should be clear for future maintainers.

6. Follow .NET conventions
   Use established patterns from Microsoft.Extensions.* libraries.

Versioning

{REPO-NAME} follows Semantic Versioning:

• Major - Breaking API changes
• Minor - New features, backward compatible
• Patch - Bug fixes, backward compatible

Given its foundational role, major version bumps are rare and carefully considered.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Cirreum Foundation Framework
Layered simplicity for modern .NET