ConfigParser

Extracts all unresolved requested includes the parsed configuration contains, including those nested inside other objects.

Since the pure core module does not support effectful IO, this hook can be used by a higher level API to resolve includes and pass them to the resolve method.

Parses and resolves the parsed HOCON input. This includes the resolving of substitution references and the merging of concatenated objects, arrays and strings.

Failures may be caused by both, the parser and resolver step.

The specified origin will be attached to every field. Origins can be used to distinguish values from a specific Config instance from those which were inherited from a fallback, which might be relevant in scenarios where relative paths need to be resolved for example.

The specified fallback will be used for resolving keys which are not present in the configuration created by this parser.

If an entire object is requested in the resulting Config instance, the keys will be merged from this parser with those present in the fallback. Simple values on the other hand will always override values with the same key in the fallback.

The specified includes contain all resources that could be loaded based on the requested resources exposed by the includes property. Keeping the actual loading separate allows the resource loading step to be separate and in a module designed for effectful operations.

The unresolved result of the parser which can be used for processing inclusions that will be resolved in the context of the hosting configuration.