Get a registered container by its name.
User's entry point for reconstructing a container from a JSON object.
User's entry point for reconstructing a container from a JSON object.
The container's type is not known at compile-time, so it must be cast (with the container's as
method) or pattern-matched (with the corresponding Factory
).
User's entry point for reading a container as JSON from a UTF-8 encoded file.
User's entry point for reading a container as JSON from a UTF-8 encoded file.
The container's type is not known at compile-time, so it must be cast (with the container's as
method) or pattern-matched (with the corresponding Factory
).
User's entry point for reading a container as JSON from a UTF-8 encoded file.
User's entry point for reading a container as JSON from a UTF-8 encoded file.
The container's type is not known at compile-time, so it must be cast (with the container's as
method) or pattern-matched (with the corresponding Factory
).
User's entry point for reading a container as JSON from a UTF-8 encoded file.
User's entry point for reading a container as JSON from a UTF-8 encoded file.
Note: fully consumes the inputStream
.
The container's type is not known at compile-time, so it must be cast (with the container's as
method) or pattern-matched (with the corresponding Factory
).
User's entry point for reconstructing a container from JSON text.
User's entry point for reconstructing a container from JSON text.
The container's type is not known at compile-time, so it must be cast (with the container's as
method) or pattern-matched (with the corresponding Factory
).
Add a new Factory
to the registry, introducing a new container type on the fly.
Add a new Factory
to the registry, introducing a new container type on the fly. General users usually wouldn't do this, but they could. This method is used internally to define the standard container types.
Get a list of registered containers as a Map
from factory name to Factory
object.
Entry point for constructing containers from JSON and centralized registry of container types.
Containers filled in Python or on remote sites are serialized as JSON that the
Factory
object can reconstruct. Reconstructed containers are fixed (immutable, cannot aggregate), but can be merged with the+
operator. (Click on the "o" in a circle in the upper-left to see theFactory
trait's documentation, which explains the difference.)To do this, the
Factory
object must dispatch JSON to the appropriate container for interpretation. It therefore manages a global registry of container types (concrete instances of theFactory
trait). General users are not expected to add to this registry, but they could if they want to.