Add TOML support #10
Merged
Add TOML support #10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
l0kod
force-pushed
the
toml
branch
4 times, most recently
from
f28c1c4 to
61b91a6
Compare
Depends on the toml feature. Simplify and rename parse_config() to parse_json(), and add a new parse_toml() helper. Signed-off-by: Mickaël Salaün <mic@digikod.net>
TOML uses snake_case, whereas JSON uses camelCase. Signed-off-by: Mickaël Salaün <mic@digikod.net>
Add TCP port control to examples. Showcase that, unlike JSON, TOML handles comments and trailing commas. Signed-off-by: Mickaël Salaün <mic@digikod.net>
Clarify the goal and explain the different use cases for JSON and TOML. Signed-off-by: Mickaël Salaün <mic@digikod.net>
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
TOML is easier for users, whereas JSON is easier for parsing.
See https://toml.io/