Closed Dark-Sol closed 1 year ago
I'm unsure if it's possible to generate a config file with the comments, as it doesn't pull from default-config.toml
in the repository. Instead, it just takes al the default values of each attribute and writes them to a file.
I'll do some more research to see if I can get the comments to be outputted. If not, the generator will have to be rewritten (shouldn't be too difficult).
I think you could leave it as is, if you want. You'd just need to write in the documentation that the behavior seen is what a user should expect if they don't copy default-config.toml
from the repository. Or when building Twitch-tui, have it pull default-config.toml
and then rename it to config.toml
, if that's possible?
Doing the second isn't possible during the build, but during runtime I could have a request fetch get the raw data from default-config.toml
and write it to config.toml
.
I'll have to consider the first, because requesting would probably better for the user in the end.
Maybe make it conditional so that it's only when it runs the configurator that it does the request fetch?
Perhaps
Alright, if you say no to the interactive config generation, then the config will generate with comments. I wasn't able to figure out how to combine interactive config generation with the args that are provided with comments, so this'll do for now.
It'll be in the next release.
Fixed in 3c111e52b74150b7511b963e533819182bc6e0e1
Describe the bug: The
config.toml
file that is generated by the configurator does not look like theexample-config.toml
file on here. None of the helpful hints that explain what each setting is and or what they could be set to are in thatconfig.toml
file.To Reproduce:
twt
at the command prompt.config.toml
file should be in%appdata%/roming/twt/
(I've posted what thatconfig.toml
file looks like below, while removing all the personal info.)System: