knf-core 0.3.2

Load, merge and emit layered JSON and TOML configuration files
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

//! The process environment, as interpolation wants to see it.
//!
//! The only place `std::env` appears in the workspace. Interpolation takes its
//! environment through a trait so that it stays deterministic and testable
//! without touching process state; this is the implementation that does not.

use crate::{Env, EnvValue};

use crate::{set, value};

/// Reads `${env:NAME}` from the real environment.
pub struct ProcessEnv;

impl Env for ProcessEnv {
    fn lookup(&self, name: &str) -> Option<EnvValue> {
        // `var` also fails on a non-UTF-8 value, which reads here as unset. That
        // is the only outcome available: bytes that are not UTF-8 cannot be
        // spliced into a JSON or TOML document either way.
        let raw = std::env::var(name).ok()?;
        // The same typing rule as `--set`'s RHS, from the same function — which
        // is the whole consistency argument for typing environment values at
        // all. Going through JSON also means this can never fabricate a
        // `Datetime`: JSON has no such type.
        let typed = value::from_json(set::json_or_string(raw.clone()));
        Some(EnvValue { raw, typed })
    }
}