-
Notifications
You must be signed in to change notification settings - Fork 7
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
Support TOML? #94
Comments
I personally dislike TOML due to syntactical complexity WRT things like arrays (will always be a controversial opinion). In this case, I would take a look at night-config as they have their own parsing implementations and zero dependencies as a result, and it has worked fine for years already. On the plus side, you can support formats like HOCON too if you like their parsing system, forking this parsing implementation would lead to a tiny file size increase for avaje-config as a whole while allowing more formats to be supported. |
I was thinking more of creating a separate module for the different formats |
If this then perhaps also add support for users to create their own parsers. Also, probably an implementation of dotenv would be simple and useful, considering dotenv-java does it in one file, <100 LOC. proposed module structure?im proposing here a LOT of formats, don't know if it fits the scope to support a lot of formats
light overview of syntactical differences between dotenv and properties
I looked at the differences a few years ago, didn't think much of it and implemented |
That recent pr adds support for custom parsers |
it probably does, but you won't find me writing a parser for them unless somebody actually needs one |
I like how it looks.
The text was updated successfully, but these errors were encountered: