Scaffold AvParser: Avalonia 12 shell with adaptive layout

Greenfield skeleton for a parser desktop app. The domain is deliberately a
placeholder — IParser<TIn,TOut> plus two sample parsers — so the shell is
runnable and verifiable end to end before real logic lands.

Layers run one way: Core (no Avalonia, no IO) <- Infrastructure <- UI <- Desktop.
UI is a class library rather than the exe so headless tests build real views
without dragging in Program.cs, Serilog or the container.

Adaptive layout is built from what Avalonia actually offers, since it has no
AdaptiveTrigger or media queries: ResponsiveLayout observes Visual.Bounds and
projects a breakpoint onto both an attached property and :compact/:medium/
:expanded pseudoclasses, with 24px hysteresis so dragging a window edge cannot
make the layout flap. Pane state lives in the view model because a style setter
loses to a local value permanently; styles own only the visual variance.

Stack notes worth remembering: Avalonia.ReactiveUI is deprecated in favour of
ReactiveUI.Avalonia, and ReactiveUI 24 runs on the Primitives engine (RxVoid,
ISequencer, Signal<T>) and no longer self-initialises. Avalonia.Headless.XUnit
12.x requires xUnit v3. InvariantGlobalization must stay false or Semi.Avalonia
throws in its static constructor.

102 tests across three projects, including headless guards for the two failures
that are otherwise completely silent: a stylesheet whose selectors match nothing,
and a light palette too low-contrast for cards to read.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Leonid Pershin
2026-08-13 16:07:08 +03:00
co-authored by Claude Opus 5
commit 3db9d4dfc6
94 changed files with 5966 additions and 0 deletions
@@ -0,0 +1,57 @@
using AvParser.Core.Parsing;
using AvParser.Core.Settings;
using AvParser.Infrastructure.Storage;
using AvParser.UI.Navigation;
using AvParser.UI.Services;
using AvParser.UI.ViewModels;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Logging;
using Serilog.Core;
namespace AvParser.UI.DependencyInjection;
/// <summary>Composition root for the presentation layer.</summary>
public static class UiServiceCollectionExtensions
{
/// <summary>Registers the view locator, shell services and every page.</summary>
/// <remarks>
/// Pages are registered twice on purpose: once under their concrete type (so tests and other
/// pages can ask for one specifically) and once under <see cref="PageViewModel"/> in the order
/// they should appear in the navigation rail.
/// </remarks>
public static IServiceCollection AddAvParserUI(this IServiceCollection services)
{
ArgumentNullException.ThrowIfNull(services);
services.AddSingleton<ViewLocator>();
services.AddSingleton<IThemeService, ThemeService>();
services.AddSingleton<INavigationService, NavigationService>();
services.AddSingleton<DashboardViewModel>();
services.AddSingleton<ParseViewModel>(static sp => new ParseViewModel(
sp.GetRequiredService<IParserCatalog>(),
sp.GetRequiredService<ISettingsService>(),
sp.GetRequiredService<ILogger<ParseViewModel>>()
));
services.AddSingleton<SettingsViewModel>(static sp => new SettingsViewModel(
sp.GetRequiredService<ISettingsService>(),
sp.GetRequiredService<IThemeService>(),
sp.GetRequiredService<IAppPaths>(),
sp.GetRequiredService<LoggingLevelSwitch>()
));
services.AddSingleton<AboutViewModel>();
// Order here is the order of the navigation rail; the first entry is the landing page.
services.AddSingleton<PageViewModel>(static sp => sp.GetRequiredService<DashboardViewModel>());
services.AddSingleton<PageViewModel>(static sp => sp.GetRequiredService<ParseViewModel>());
services.AddSingleton<PageViewModel>(static sp => sp.GetRequiredService<SettingsViewModel>());
services.AddSingleton<PageViewModel>(static sp => sp.GetRequiredService<AboutViewModel>());
services.AddSingleton<ShellViewModel>(static sp => new ShellViewModel(
sp.GetRequiredService<INavigationService>(),
sp.GetRequiredService<IThemeService>()
));
return services;
}
}