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

cannot include yaml file #14

Open
davidkarlsen opened this issue Oct 17, 2017 · 0 comments
Open

cannot include yaml file #14

davidkarlsen opened this issue Oct 17, 2017 · 0 comments

Comments

@davidkarlsen
Copy link

If I have a .conf file:

{ a : { include required(classpath("myyaml")) } }

I will get a stack-trace with:

Caused by: java.io.IOException: resource not found on classpath: myyaml.conf
	at com.typesafe.config.impl.Parseable$ParseableResources.rawParseValue(Parseable.java:735)
	at com.typesafe.config.impl.Parseable$ParseableResources.rawParseValue(Parseable.java:710)
	at com.typesafe.config.impl.Parseable.parseValue(Parseable.java:180)
	... 47 more

and if I give a suffix:

{ a : { include required(classpath("myyaml.yaml")) } }

I will get:

Caused by: java.io.IOException: resource not found on classpath: myyaml.yaml.conf
	at com.typesafe.config.impl.Parseable$ParseableResources.rawParseValue(Parseable.java:735)
	at com.typesafe.config.impl.Parseable$ParseableResources.rawParseValue(Parseable.java:710)
	at com.typesafe.config.impl.Parseable.parseValue(Parseable.java:180)
	... 47 more

Seems this is not supported? But from the github readme I see:

In short, HOCON combines YAML, JSON, and Properties files into a single format. On most cases, YAML, JSON, and Properties formats are all valid HOCON--- and it can be mixed and matched at will. Check out the HOCON docs for more detail on the format.
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

1 participant