Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey! Love the library, I use it a lot for embedding configuration and credentials into embedded devices.
The
failing-config
example I've added basically describes the use-case that motivated this: I wanted a config that requires some fields (e.g.wifi_ssid
) to be set but doesn't necessarily need other fields (e.g.wifi_passkey
, ...). I could provide defaults for everything then check for non-default values at runtime, but that's verbose and negates the awesomeness of this crate: being able to control the config at compile-time.This is backwards compatible except for error messages:
#[default(...)]
behaves identically, users have to add#[required]
to see any new behaviour.First two commits are just housekeeping, 3rd commit is implementation+documentation.