Skip to content
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

Switch from INI to TOML #20

Closed
justjosias opened this issue Jul 31, 2020 · 2 comments
Closed

Switch from INI to TOML #20

justjosias opened this issue Jul 31, 2020 · 2 comments

Comments

@justjosias
Copy link
Contributor

The TOML configuration language is very similar to INI, but has a complete standard.

@RasmusLindroth
Copy link
Owner

I tried TOML first I think and If I recall correctly I settled with ini because of the available parsing packages. This package preserved comments better than other packages.

Now I don't see why I should change as it would break compatability with previous versions and this seems to work just fine.

I will leave this open if you have some more reason why it would be better to switch. Thanks for the input.

@justjosias
Copy link
Contributor Author

I believe the file itself is both valid INI and TOML. The main difference would be spacing and the file extension. Also, both could be supported for a release cycle if you really wanted.

Also, I have used go-toml several times, and it works very well.

I understand if you don't want to though. I was bringing up a suggestion from my experience with both formats.

This package preserved comments better than other packages.

Can you elaborate here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants