UniConfig Config Panel

ConfigUI (binary uniconfig) opens ordinary config files — INI, YAML, TOML, SDLang, JSON, tfvars — and shows the same settings widgets every time: labels, enums, toggles, descriptions, and fields the author never wrote.

The reusable engine is uniconfig-core (UniConfig). DevCentr and third-party apps depend on the engine without pulling a GUI.

Engine, vocabulary, form binder, ConfigUI shell

How vocabulary works

Syntax parsers live in the engine. Semantic vocabulary (which fields exist) ships with your app:

  1. Add uniconfig/catalog.sdl + JSON Schema beside your product.

  2. Call registerCatalogSource on startup — writes a pointer in %LOCALAPPDATA%\UniConfig\catalog-index.sdl.

  3. ConfigUI lazy-loads that catalog when a matching file opens.

See Ship vocabulary with your app. You do not open PRs to UniConfig for normal app settings.

Bundled fallback-catalog/ beside the executable covers Git, DUB, Terraform, and similar tools that never ship their own vocabulary.

Get it

uniconfig .\fixtures\sample.gitconfig
uniconfig register-catalog --id com.example.app --catalog .\uniconfig\catalog.sdl --repository https://github.com/example/app
uniconfig dump .\fixtures\sample.gitconfig