-
-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement TOML difference #186
Comments
Should it be cli command or stderr message after decoding? |
@willbasky Under one issue I proposed the following data type as a result of decoding TOML: data Result a
= Failure String
| Warning [DecodeWarning] a
| Success a I believe this should be a separate function(s) in some experimental |
Ok. Then for this issue it will be within result message And for other issue it will be separate function. And maybe we will find some other useful functions to be invented. |
Now we have
|
@willbasky In future we might want to change |
So, now, should it be in separate module. Some decode-like function that returns |
@willbasky Exactly |
The function is starting to become more useful. So here is the roadmap for implementing the feature:
|
Currently if you implement
Codec
for file that contains more fields that you need,tomland
will use only those fields that you specified. However, sometimes it's desired to tell about redundant or unused fields. In JSON it is completely okay to ignore some fields, but in TOML static configuration having some fields in the config may lead to frustration in the future. It would be nice to have some way of telling which fields were not used.The text was updated successfully, but these errors were encountered: