summaryrefslogtreecommitdiff
path: root/Cargo.toml
Commit message (Collapse)AuthorAge
* Use released `maud` crate.Owen Jacobson2020-07-31
| | | | The maintainer has put up-to-date packages on crates.io, so let's use 'em for hygiene.
* Switch from quickcheck to proptest.Owen Jacobson2020-06-26
| | | | | | | | | | | | | The argument is as given in the proptest docs at <https://altsysrq.github.io/proptest-book/proptest/vs-quickcheck.html>. I've found that the resulting tests are somewhat clearer, and that the tools for working with test case generation are more useful. The other killer feature is recalling test failure examples from run to run. This change includes at least one bug found while testing the port! Finally, if <https://github.com/AltSysrq/proptest/issues/179> is to be believed, proptest is considerably closer to supporting async tests.
* Stop releasing semver versions.Owen Jacobson2020-06-17
| | | | That was an experiment that didn't really go anywhere. There are no meaningful "versions" of this software - it runs on a single host, and there are no compatibility promises.
* (cargo-release) start next development iteration 0.4.2-alpha.0Owen Jacobson2020-06-16
|
* (cargo-release) version 0.4.1Owen Jacobson2020-06-16
|
* Set up travis for continuous testingOwen Jacobson2020-06-16
|
* Add a README and project metadata.Owen Jacobson2020-06-16
|
* (cargo-release) start next development iteration 0.4.1-alpha.0Owen Jacobson2020-06-05
|
* (cargo-release) version 0.4.0Owen Jacobson2020-06-05
|
* (cargo-release) start next development iteration 0.3.1-alpha.0Owen Jacobson2020-06-04
|
* (cargo-release) version 0.3.0Owen Jacobson2020-06-04
|
* (cargo-release) start next development iteration 0.2.1-alpha.0Owen Jacobson2020-06-04
|
* (cargo-release) version 0.2.0Owen Jacobson2020-06-04
|
* Markdown support.Owen Jacobson2020-06-04
| | | | | | | | This accomplishes two things: 1. The og cards and page title no longer contain half-baked markup. Instead, they show the markdown equivalent, which is generally pretty friendly. In other words, the page title is "Have you checked `resolv.conf`?" and not "Have you checked <code>resolve.conf</code>?" 2. Phrases can now start with terms other than "Have you checked".
* Port things-to-check to Rust as a learning exercise.Owen Jacobson2020-06-03
This is somewhat overengineered in places, but does the job and exposes broadly the same interfaces as the Python version. Builds with emk/rust.