omnigraph/crates/omnigraph-server
Ragnor Comerford eb3c36d8aa
feat(cli,server): warn on deprecated config at load; scaffold version: 1
Surface the config deprecation notices at load: the CLI prints them via
`eprintln!` in `load_cli_config`; the server logs them via `tracing::warn!` in
`load_server_settings` (a no-op under tests with no subscriber). `omnigraph init`
now scaffolds a `version: 1` config using `storage:` instead of the legacy `uri:`.

Migrate the shared test fixtures (`support::local_yaml_config` →
`version: 1` + `storage:`; `remote_yaml_config` → `version: 1` + `servers:`/`server:`)
to the current schema so they don't trip the new warnings; the resolved `.uri` is
unchanged, so the tests behave identically. The no-`version:` notice is gated on a
loaded config file, so commands with a bare URI and no `omnigraph.yaml` stay quiet
(verified by the existing command-deprecation tests, which still pass). Extends the
`init` test for the scaffold shape and adds a legacy-config-warns test.
2026-06-04 08:48:04 +02:00
..
examples feat: inline query strings in CLI and HTTP server (#110) 2026-05-29 13:41:54 +02:00
src feat(cli,server): warn on deprecated config at load; scaffold version: 1 2026-06-04 08:48:04 +02:00
tests fix(server): reject remote graph entries at config load 2026-06-03 17:41:38 +02:00
Cargo.toml refactor: extract omnigraph-api-types crate from omnigraph-server 2026-06-03 11:14:19 +02:00