org.ekrich.config.parser
package org.ekrich.config.parser
Type members
Classlikes
trait ConfigDocument
Represents an individual HOCON or JSON file, preserving all
formatting and syntax details. This can be used to replace
individual values and exactly render the original text of the
input.
formatting and syntax details. This can be used to replace
individual values and exactly render the original text of the
input.
Because this object is immutable, it is safe to use from multiple threads and
there's no need for "defensive copies."
there's no need for "defensive copies."
Do not implement interface ConfigDocument; it should only be
implemented by the config library. Arbitrary implementations will not work
because the library internals assume a specific concrete implementation.
Also, this interface is likely to grow new methods over time, so third-party
implementations will break.
implemented by the config library. Arbitrary implementations will not work
because the library internals assume a specific concrete implementation.
Also, this interface is likely to grow new methods over time, so third-party
implementations will break.
trait ConfigNode
A node in the syntax tree for a HOCON or JSON document.
Note: at present there is no way to obtain an instance of this interface, so
please ignore it. A future release will make syntax tree nodes available in
the public API. If you are interested in working on it, please see: <a
href="https://github.com/lightbend/config/issues/300"
please ignore it. A future release will make syntax tree nodes available in
the public API. If you are interested in working on it, please see: <a
href="https://github.com/lightbend/config/issues/300"
Because this object is immutable, it is safe to use from multiple threads and
there's no need for "defensive copies."
there's no need for "defensive copies."
Do not implement interface ConfigNode; it should only be
implemented by the config library. Arbitrary implementations will not work
because the library internals assume a specific concrete implementation.
Also, this interface is likely to grow new methods over time, so third-party
implementations will break.
implemented by the config library. Arbitrary implementations will not work
because the library internals assume a specific concrete implementation.
Also, this interface is likely to grow new methods over time, so third-party
implementations will break.