Skip to content

cannot include yaml file #14

@davidkarlsen

Description

@davidkarlsen

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions