35
🛠️ TaskCrafter - CLI task scheduler
(github.com)
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Community icon from opensource.org, but we are not affiliated with them.
you must be new at this or have some sort of Stockholm syndrome
:D Not really, but the thing with stockholm syndrom maybe describes me quite well :D. However, if I'd have to decide to do a config file, I would always rather take yaml than json.
i mean, JSON is ugly and has its own problems, but it doesn’t have 6 legal values for boolean types. my opinion is that if you can’t do it in TOML you shouldn’t be doing it in config
ETA: if you like this and it’s useful to you, i don’t want to discourage you. i’ve just been fighting with yaml config all week
Thank you for your feedback.
The good old X vs Y. I think its a matter of use-case and personal preference. The decision to pick yaml is solely because readability, which is, above what toml has to offer with its single-dimension. On the other side, yes, yaml has its own quirks such as primitive boolean (yes, true, on) and whitespace sensitivity;
still, yaml is still preferred type when we're talking devops.
I'll put this on a nice to have list- I'm quite sure the toml OR yaml for that matter, has an option to convert one way or another :)
Update: I've added the issue to the project.