state: Shift the state tree to it's own set of files #143
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@crosbymichael was adding these to existing Go files to avoid having
a lot of files. But 7232e4b (specs: introduce the concept of a
runtime.json
, 2015-07-30, #88) split the runtime-configuration intotwo file sets (one rooted in
config.go
forconfig.json
and anotherrooted in
runtime_config.go
forruntime.json
). In the face of atwo-set split for a single task (feeding the runtime while it
manipulates the container lifecycle), it seems odd to push the type
definition for a completely different task (sharing
container/application state with other tools) into an existing file
set.
Spun off from here. See also #126, which standardizes the JSON /
doc / Go naming pattern.