MiniConf is a no_std minimal run-time settings configuration tool designed to be run on top of
any communication means. It was originally designed to work with MQTT clients and provides a default
implementation using minimq as the MQTT client.
Miniconf provides an easy-to-work-with API for quickly adding runtime-configured settings to any embedded project. This allows any internet-connected device to quickly bring up configuration interfaces with minimal implementation in the end-user application.
MiniConf provides a Miniconf derive macro for creating a settings structure, e.g.:
```rust
use miniconf::Miniconf;
struct NestedSettings { inner: f32, }
struct MySettings { initial_value: u32, internal: NestedSettings, } ```
A setting value must be configured via a specific path. Paths take the form of variable names
separated by slashes - this design follows typical MQTT topic design semantics. For example, with
the following Settings structure:
```rust
struct Data { inner: f32, }
struct Settings { initial_value: u32, internal: Data, } ```
We can access Data::inner with the path internal/inner.
Settings may only be updated at the terminal node. That is, you cannot configure
<device-id>/settings/internal directly. If this is desired, instead derive MiniconfAtomic on the
struct Data definition. In this way, all members of struct Data must be updated simultaneously.
MiniConf relies on using serde for defining a
de/serialization method for settings. Currently, MiniConf only supports serde-json de/serialization
formats, although more formats may be supported in the future.