Open StuartHarris opened 1 year ago
Could this CLI also help "install" capabilities? It would be cool if there were a convention for packaging up "default" shell implementations in capability crates.
crux add --cap [name] --shell [name]
# Copies the default shell implementation for [cap] into [shell]
Yep, love it! The next thing we want to do is to refactor the examples a bit more so that all the "boilerplate" code is in its own files — this is partially done already, but needs a bit more love — so that the diffs make more sense. Then the shell-side code for the capabilities, which is very much generic, can be added, analysed, and fixed in the same way. And we can have the relevant subcommands/flags on the cli as you suggest.
Distributing those implementations is definitely the plan @wasnotrice, but we're hoping to allow them to be distributed in "fat crates" if you will, so no additional tooling is required... but we're not yet sure exactly how that might work.
We'll need a pattern for how that code is found and linked into the shells, so that we can then help verify all that with the doctor
like Stu is suggesting
CLI tool
Some ideas for a simple Crux CLI that can analyze, validate, fix, and create Crux projects within a workspace. Let's start simple, and evolve over time.
Some ideas:
To do list
Crux.toml
diff --paths-only
fix
- Replace file with template generated fileinit
/new
/add
Crux.toml
doctor