WebSvc.ConfigVisualizer 1.0.3

WebSvc.ConfigVisualizer

Standalone editor for the tenant dashboard config JSON that CrudApi's AI pipeline (CrudConfigApplicationService) generates and pushes to git at mydash/tenants-config/{db}.json.

• Tree/field-list/inspector editor over the config's groups[] → entities[] → fields shape — fixes gaps the generator leaves behind (e.g. a relation field's labelFields always emitted empty).
• No SQL storage of its own — same "JSON-file session" shape as WebSvc.SqliteAdmin. Draft edits live entirely in the browser; nothing is written until you publish.
• Publishing creates a new git commit via WebSvc.GitOps's IGitOpsService (PushFileAsync) — the same call the generator itself uses, so there's no second write path.
• Version history and restore read commit history directly from the GitHub REST API (GitHub:Owner/GitHub:Repo/GitHub:Token, the same IConfiguration keys HostSettingsConfigBridge already populates for WebSvc.GitOps) — IGitOpsService itself has no history capability, so this is a small, independent, read-only client.
• Independent login at /configvisualizer/login, plus a signed, short-lived, single-use, Global-Admin-only auto-login handoff from CrudAdmin's Databases page, scoped per database.

Setup

builder.Services.AddConfigVisualizer(builder.Configuration);
// ...
app.UseConfigVisualizer();
// ...
app.MapConfigVisualizer();

Requires WebSvc.GitOps's IGitOpsService and GitHub credentials (GitHub:Owner, GitHub:Repo, GitHub:Token) already registered/configured in the host — this package doesn't own that setup, it only consumes it.

Configuration (appsettings.json, section ConfigVisualizer): RootPath (default /configvisualizer), DataDirectory (default ConfigVisualizerData/ under the app's base directory — kept separate from sibling packages' data folders), Username/ PasswordHash (the Global-Admin break-glass manual-login credential), SessionHours, ConfigPathPrefix (default mydash/tenants-config), Branch (default main).

To enable the signed cross-app handoff from CrudAdmin's Databases page, also call AddCrudAdmin(...) in the same host — ConfigVisualizer shares whatever IDataProtectionProvider key ring is already registered (typically CrudAdmin's), so no AddDataProtection() call is needed here.

Explicitly out of scope

Schema introspection, the AI grouping call, and generate-config itself all stay in CrudApi's own CrudConfigApplicationService — this package only ever reads, edits, and republishes the JSON that pipeline already produces.