Move crates to dedicated crates
folder
#416
Merged
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.
There is no convention that I can find per se that says that workspaces should be organized like this, with a
crates
folder rather than putting all of the crates in the root. The closest thing I could find is this blog post by the creator of Rust Analyzer.However, I think that this is the beginning of a list of changes I want to make:
crates
folder to reduce clutter in the repository's root.src
folder and its actual dependencies into a new crate namedchia-consensus
.chia
into a meta-crate that re-exports each of the workspace's crates as togglable features that are enabled by default.ff-tests
,cl
,test-bundles
, andgenerator-tests
folders.docs
into actual documentation in the root of the appropriate crate.chia_rs
in Rust (maybechia-tools
should live there?).