This prepares the crate versions for a new release. The version bumps were determined by the `cargo-semver-checks` tool. However, there were some issues with the `radicle-fetch` crate – where when attempting to check it, it was unable to compile due to the previous version expecting the kind of `Doc` with a generic parameter. I believe this is due to the version for `radicle` being specified as simply `0`. This prompted changing the version specifications to use `major.minor` for all the internal crates. This, for example, would mean that `radicle-fetch` that relies on `0.15` can use `>=0.15.0,<0.16.0` – allowing any patch versions but must require a minor version bump. |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
README.md
radicle-cli-test
Test your CLI with the help of markdown descriptions.
Example
Test flows are described in markdown like this example:
# Echoing works
When I call echo, it answers:
```
$ echo "ohai"
ohai
```
Say this is placed in kind-echo.md, this is what the corresponding test case
would look lke:
use std::path::Path;
use radicle_cli_test::TestFormula;
#[test]
fn kind_echo() {
TestFormula::new()
.file(Path::new("./kind-echo.md"))
.unwrap()
.run()
.unwrap();
}