miniconf
miniconf copied to clipboard
quartiq
Rust serialize/deserialize/access reflection for trees (no_std, no alloc)
There are a bunch of [serde field attributes](https://serde.rs/field-attrs.html) that would be useful to forward/leverage. E.g. * [x] `getter` #199 * [x] `skip` #183 * [ ] `alias` * [x] `rename`...
Looks more "idiomatic" ... Let's explore it. https://github.com/sbtinstruments/aiomqtt
Posting it here as it affects all stabilizer/stabilizer-fls/booster/thermostat-mqtt/thermostat-eem. This should be integrated into the docs to give people a head start. Also IMO the common docs that are more miniconf-specific...
If a setting is an `Option`, and thus run-time dependent, it will still be provided in the `list` output of the MQTT client. This could be acceptable, but we should...
Currently, it doesn't seem possible to do the following properly: ```rs struct A { inner: T, outer: u32, } ``` We would need to annotate the `inner: T` with `#[tree(depth(Y))]`,...
As part of the derive macro, it would be useful to use a `Key` to look up the docstring related to the entry. For example: ```rust #[derive(miniconf::Tree)] struct Settings {...
They would be very much like `Option` (without the `None` case) and be a general pass-through for all miniconf depths.
would only change their variant at runtime outside `Miniconf`, i.e. be like option, untagged enum They would implement exactly one depth: the max of the inner types.
play with https://github.com/rust-phf/rust-phf
There are some use case issues with understanding string escape sequences on the Python client for miniconf. Based on the user shell, a variety of escape sequences are required to...