This repository was archived by the owner on Feb 28, 2021. It is now read-only.
Properly isolate and document core state entities #205
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.
As part of the restructuring of the registry spec and the
core
package we add theradicle_registry_core::state
module and move all definitions of state entities there.This PR is split into two commits: The first removes the
registry-spec
package as it is not needed anymore. The state objects and documentation are now part ofcore::state
. The errors that were part of theregistry-spec
have not been migrated to a different place yet but they are outdated anyways.The second commit adds the
state
module and the necessary documentation. We also document how to document state entities in thecore
README.