sjgandClaude Opus 5
da58a004fe
The setup wizard, the server and the client each carried their own idea of what a valid config looks like: trx-configurator validated with hand-written toml_edit key lists while the binaries validated with serde plus their own validate(). Nothing kept the three in sync. Move ServerConfig, ClientConfig, the section loader, the shared validators and the endpoint-URL parsing into a new trx-config crate that all three depend on, so there is one definition of the config to drift from. The binaries keep a thin crate::config re-export so their internal paths are unchanged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SyX26FCpMQxiBoC7r5K1A7 Signed-off-by: Stan Grams <sjg@haxx.space>
23 lines
704 B
Rust
23 lines
704 B
Rust
// SPDX-FileCopyrightText: 2026 Stan Grams <sjg@haxx.space>
|
|
//
|
|
// SPDX-License-Identifier: GPL-2.0-or-later
|
|
|
|
//! Configuration types shared by `trx-server`, `trx-client` and
|
|
//! `trx-configurator`.
|
|
//!
|
|
//! Keeping the structs, the loader and the validators in one crate means the
|
|
//! setup wizard checks a config with exactly the same code the binaries load
|
|
//! it with, so the two can never drift apart.
|
|
|
|
pub mod client;
|
|
pub mod file;
|
|
pub mod server;
|
|
pub mod shared;
|
|
pub mod url;
|
|
|
|
pub use client::ClientConfig;
|
|
pub use file::{ConfigError, ConfigFile};
|
|
pub use server::ServerConfig;
|
|
pub use shared::{validate_log_level, validate_tokens};
|
|
pub use url::{parse_audio_url, parse_remote_url, RemoteEndpoint};
|