Struct ServiceConfig 

pub struct ServiceConfig {
    pub strategy: Option<Strategy>,
    pub rule_sets_file_paths: Option<Vec<String>>,
    pub rule_sets: Vec<RuleSet>,
    pub middlewares_file_paths: Option<Vec<String>>,
    pub fallback_respond_dir: String,
}

Fields

strategy: Option<Strategy>

How multiple matching rules in a set are resolved. Currently first_match is the only recognised value.

rule_sets_file_paths: Option<Vec<String>>

Paths to rule-set TOML files. User-editable via the [service] table.

rule_sets: Vec<RuleSet>

Loaded rule sets in the same order as rule_sets_file_paths. Populated at startup by Config::new (this field is #[serde(skip)] because it comes from loading the files listed above, not from the config TOML itself).

middlewares_file_paths: Option<Vec<String>>

Paths to Rhai middleware files. Compilation happens in the server crate — config only holds the paths.

fallback_respond_dir: String

Filesystem directory served by the dyn-route fallback.

Implementations

impl ServiceConfig

pub fn validate(&self) -> bool

Validate that every rule set and the fallback respond dir are internally consistent.

Why validation stays in config, not routing

Validation inspects cross-cutting state (file existence of the fallback dir, every rule’s respond.file_path, etc.). All that state is assembled by config loading. Routing has per-rule validators, which this method calls.

Trait Implementations

impl Clone for ServiceConfig

fn clone(&self) -> ServiceConfig

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Default for ServiceConfig

fn default() -> Self

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for ServiceConfig

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Display for ServiceConfig

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.