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

Properties file #111

Open
axos88 opened this issue Jan 18, 2018 · 2 comments
Open

Properties file #111

axos88 opened this issue Jan 18, 2018 · 2 comments

Comments

@axos88
Copy link

axos88 commented Jan 18, 2018

Isn't a properties file a valid HOCON? Is there any reason it is not supported? The HOCON parser should be able to parse a properties file, should it not?

@lindboe
Copy link

lindboe commented Jan 18, 2018

Quick answer: Check out the doc from the HOCON spec, especially the linked section, to understand why HOCON can't parse all properties files. https://github.com/lightbend/config/blob/master/HOCON.md#note-on-java-properties-similarity

They do have a recommendation earlier in the spec about how you should go about merging properties and JSON/HOCON data if you need to.

@axos88
Copy link
Author

axos88 commented Jan 20, 2018

Thanks, might want to include this info / link in the readme, as they are cornercases, that are possibly rare and can be ignored by most users.

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