mirrors/arti.git/crates/arti-client/src/config.rs, branch arti-v1.4.6

arti-client: Re-export `ConfigurationSources`

2025-06-11T09:45:02Z

This commit re-exports `ConfigurationSources` in `arti_client::config`. The similar `ConfigurationSource` is already publicly exported, but it unfortunately it is pretty useless without a `ConfigurationSources` to which it belongs.

arti,arti-client: Add an option to override required protocols

2025-04-16T23:06:51Z

(This isn't a boolean, because we really don't want people ignoring all possible required protocols.)

Move base CfgPathResolver for arti-client back to tor-config-path.

2024-12-09T20:23:43Z

This time, we make explicit that it is a _base_ resolver, and that it is client-only.

arti-client: change test to use path resolver from `TorClientConfig`

2024-11-18T15:01:56Z

tor-config-path: remove `Option` from resolver value

2024-11-18T15:01:56Z

arti-client: add path resolver to `TorClient` and `TorClientConfig`

2024-11-18T15:01:56Z

Rather than using `arti_client::config::path_resolver()`, third-party code can get the path resolver using `TorClientConfig`s `AsRef` impl instead.

arti-client: add a more-comprehensive cfg variable test

2024-11-18T15:01:56Z

arti-client: moved two tests from tor-config-path

2024-11-18T15:01:56Z

Also updated to use the `PATH_RESOLVER` resolver.

update `CfgPath::path` to use a `CfgPathResolver`

2024-11-18T15:01:56Z

This is a big change across multiple crates since there isn't a good way to break it up. This changes the signature of `CfgPath::path` to: ``` pub fn path(&self, path_resolver: &CfgPathResolver) -> Result { ``` Making this change means that our global `CfgPathResolver` needs to be stored in the 'arti-client' library instead of `tor-config-path`, and must be passed through to anything that calls `path` to expand the variables.

tor-config: removed re-export of `CfgPath`

2024-11-04T14:58:43Z

Also updated other packages to get `CfgPath` directly from `tor-config-path' instead of 'tor-config'.