ConfigConcatenation
Related Docs:
object ConfigConcatenation
| package impl
Places the value inside a Config at the given key.
Places the value inside a Config at the given key. See also
ConfigValue#atPath.
key to store this value at.
a Config instance containing this value at the given key.
Places the value inside a Config at the given path.
Places the value inside a Config at the given path. See also
ConfigValue#atKey.
a Config instance containing this value at the given
path.
Super-expensive full traversal to see if descendant is anywhere underneath this container.
Super-expensive full traversal to see if descendant is anywhere underneath this container.
The origin of the value (file, line number, etc.), for debugging and error messages.
The origin of the value (file, line number, etc.), for debugging and error messages.
where the value came from
This is used when including one file in another; the included file is relativized to the path it's included into in the parent file.
This is used when including one file in another; the included file is
relativized to the path it's included into in the parent file. The point
is that if you include a file at foo.bar in the parent, and the included
file as a substitution ${a.b.c}, the included substitution now needs to
be ${foo.bar.a.b.c} because we resolve substitutions globally only after
parsing everything.
value relativized to the given path or the same value if nothing to do
Renders the config value to a string, using the provided options.
Renders the config value to a string, using the provided options.
If the config value has not been resolved (see Config.resolve()]]), it's possible that it can't be rendered as valid HOCON. In that case the rendering should still be useful for debugging but you might not be able to parse it. If the value has been resolved, it will always be parseable.
If the config value has been resolved and the options disable all HOCON-specific features (such as comments), the rendering will be valid JSON. If you enable HOCON-only features such as comments, the rendering will not be valid JSON.
the rendering options
the rendered value
Renders the config value as a HOCON string.
Renders the config value as a HOCON string. This method is primarily intended for debugging, so it tries to add helpful comments and whitespace.
If the config value has not been resolved (see Config.resolve()), it's possible that it can't be rendered as valid HOCON. In that case the rendering should still be useful for debugging but you might not be able to parse it. If the value has been resolved, it will always be parseable.
This method is equivalent to
render(ConfigRenderOptions.defaults()).
the rendered value
Replace a child of this value.
Replace a child of this value. CAUTION if replacement is null, delete the child, which may also delete the parent, or make the parent into a non-container.
Called only by ResolveContext.resolve().
Called only by ResolveContext.resolve().
state of the current resolve
where to look up values
a new value if there were changes, or this if no changes
Returns the value as a plain Java boxed value, that is, a String,
Number, Boolean, Map,
List, or null, matching the #valueType
of this ConfigValue.
Returns the value as a plain Java boxed value, that is, a String,
Number, Boolean, Map,
List, or null, matching the #valueType
of this ConfigValue. If the value is a ConfigObject or
ConfigList, it is recursively unwrapped.
a plain Java value corresponding to this ConfigValue
The ConfigValueType of the value; matches the JSON type schema.
The ConfigValueType of the value; matches the JSON type schema.
value's type
Returns a new value computed by merging this value with another, with keys in this value "winning" over the other one.
Returns a new value computed by merging this value with another, with keys in this value "winning" over the other one.
This associative operation may be used to combine configurations from multiple sources (such as multiple configuration files).
The semantics of merging are described in the spec for HOCON. Merging typically occurs when either the same object is created twice in the same file, or two config files are both loaded. For example:
foo = { a: 42 }
foo = { b: 43 }Here, the two objects are merged as if you had written:
foo = { a: 42, b: 43 }Only ConfigObject and Config instances do anything in
this method (they need to merge the fallback keys into themselves). All
other values just return the original value, since they automatically
override any fallback. This means that objects do not merge "across"
non-objects; if you write
object.withFallback(nonObject).withFallback(otherObject),
then otherObjectwill simply be ignored. This is an
intentional part of how merging works, because non-objects such as
strings and integers replace (rather than merging with) any prior value:
foo = { a: 42 }
foo = 10Here, the number 10 "wins" and the value of foo would be
simply 10. Again, for details see the spec.
a new object (or the original one, if the fallback doesn't get used)
Returns a ConfigValue based on this one, but with the given
origin.
Returns a ConfigValue based on this one, but with the given
origin. This is useful when you are parsing a new format of file or setting
comments for a single ConfigValue.
the origin set on the returned value
the new ConfigValue with the given origin
1.3.0