MudBlazor.Extensions

Playzor is a suite of packages designed for code playgrounds and editors, providing compiler capabilities, Blazor components, and server-side support. The ecosystem is split into several specialized packages:

Note on Dependencies: Playzor.Core depends on MudBlazor.Extensions to provide ambient references for MudBlazor and MudEx to the user's code.

MudBlazor.Extensions provides several utility categories to simplify common Blazor development tasks:

Styling Utilities

• Color Utilities: Color manipulation, conversion, and generation.
• CSS Builder: Dynamic CSS class building with conditional logic.
• Style Builder: Dynamic inline style building.
• Size Utilities: Size calculations, conversions, and parsing.

Helper Utilities

• MudExJsonHelper: JSON serialization and manipulation.
• MudExFonts: Font management and loading.
• MudExThemeHelper: Theme creation and manipulation.
• BrowserFileExt: File handling extensions.
• EnumHelper: Enum utility methods.
• ComponentHelper: Component reflection and creation.
• LocalizationStringHelper: Localization support.

MudExObjectEdit is a component that automatically generates user interfaces for editing objects. It uses your model's properties and metadata (like DataAnnotations) to build forms, supporting automatic validation via DataAnnotations or FluentValidation. It supports grouping via tabs, accordions, or dock panels, and allows for highly customized layouts and conditional rendering.

<!-- Basic usage with MudExObjectEditForm -->
<MudExObjectEditForm OnValidSubmit="@OnSubmit" Value="@MyModel" />

@code {
    private MyModel MyModel = new MyModel();

    private void OnSubmit()
    {
        // Handle valid submission
        Console.WriteLine($"Name: {MyModel.Name}");
    }
}

The MudExCssBuilder class is a utility for dynamically constructing CSS class strings. It is thread-safe (using concurrent dictionaries) and implements IAsyncDisposable to clean up any disposable objects stored during the building process.

Key features include:

• Conditional Class Addition: Add classes based on boolean conditions or predicates (Func<bool>).
• Style Integration: Extract classes from style objects or style strings asynchronously.
• Fluent API: Use factory methods like From to initialize the builder.
• Attribute Support: Add classes directly from an IReadOnlyDictionary<string, object> of attributes.

// Example conceptual usage
var builder = MudExCssBuilder.Default;
builder.AddClass("my-base-class");
builder.AddClass("conditional-class", someCondition);
string finalClass = builder.Build();

The BrowserFileExtensions utility provides several capabilities for managing files in the browser:

• File Icons: Retrieve appropriate icons for specific file types.
• Data URLs: Convert IBrowserFile objects into Data URLs for easy previewing.
• Type Detection: Detect file types and MIME types.

The MudBlazor.Extensions.Tests project organizes tests into two distinct categories:

• UITests: Located in the UITests folder. These focus on end-to-end user interface behaviors using Playwright.
• UnitTests: Located in the UnitTests folder. These focus on testing individual functional units of the code.

Both categories utilize xUnit as the underlying testing framework.

The documentation is organized into several functional areas within the docs/ directory:

• index.md: Homepage
• getting-started/: Installation and setup guides
• components/: Documentation for specific components
• extensions/: Documentation for extension methods
• utilities/: Documentation for utility classes
• services/: Documentation for services
• api/: Full API reference
• about/: License and contributing information
• stylesheets/: Custom CSS files
• javascripts/: Custom JavaScript files

Configuration is managed via the mkdocs.yml file in the root.

The system uses a BrandingService to resolve visual identity based on the request hostname. This allows a single codebase to serve different 'brands' (e.g., mudex.org vs playzor.net).

Resolution Logic:

• The service maps window.location.hostname to a specific Brand record.
• If the hostname is unknown or localhost, the brand can be overridden using the ?brand= query parameter.

Brand Properties: A Brand record includes Name, LogoUrl, PrimaryColor, CanonicalHost, DefaultCulture, DefaultPackages, and a MudTheme (containing both Light and Dark palettes). This affects the landing page, toolbars, embed footers, and default templates used in the playground.