usage
prover-suite
| usage | prover-suite | |
|---|---|---|
| 1 | 1 | |
| 56 | - | |
| - | - | |
| 9.3 | - | |
| 11 days ago | - | |
| Rust | ||
| MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
usage
-
CLI user experience case study
it's not complete, but I've been thinking about this problem for years and have been thinking about how to solve it.
I am working on it here: https://github.com/jdx/usage
It's mostly just a README right now, and I'm still iterating on it, talking to friends, but I think I'm getting close. My hope is within the next month or two I might have a usable alpha release of it.
If you have any thoughts on my desig lmk.
prover-suite
-
CLI user experience case study
Ive sort of managed to implement something to this effect in python, and from another comment made me consider yanking it out to its own library.
I made a process where args are now in a toml file, with some various data for different operations, like whether its available in the CLI or API library, its arg flags, help text required value type, etc. From that, i can generate argparse args, documentation, code for other things, etc. Right now im generating args, docs, and a js code block from the same structure.
Heres the toml file: https://gitlab.com/accidentallythecable-public/prover-suite/...
And some docs that were generated from that: https://gitlab.com/accidentallythecable-public/prover-suite/...
Maybe it will give you some ideas on yours