Should individual toml config file fields be optional?

[5tefan]

In experimenting with the tv.toml config file, it seems to fail to parse and take effect if only some options are present. They must all be present. This was a bit confusing at first!

I think making each field in tv.toml optional would improve the user experience and make the tool more powerful/flexible.

[alexhallam]

That makes a lot of sense. I agree, optional config parameters should be available to users.

[zhengpd]

@alexhallam Thanks for the pretty tv tool. Optional config would be good. Or it should be mentioned that "all options must be present in tv.toml" in README. I really didn't know why my 3 lines tv.toml never work (only wanted to change colors), until seeing this issue.

They must all be present.

Thanks @5tefan for the tip.

[alexhallam]

Okay, I will get working on this. Thanks for using the tool and contributing issues and suggestions for improvements.

[alexhallam]

Hi guys. I took another try at this, but did not have success. I just added a comment to the readme. #126 . I am going to leave a reproducible example from the Rust Playground here for anyone to try to tackle.

Here is how to run the rust playground example. The example works as is, but if you add a comment # in front of one of the fields defined in file_contents such as extend_rows you will see that the config returns None. A working example would return a config, but with the one field that is missing not defined.