lytedev/taskr
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

More readme

Browse source
This commit is contained in:
Daniel Flanagan 2024-04-20 08:38:15 -05:00
parent 663d0ee81a
commit 7e9900ffd5
1 changed files with 17 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

27
readme.md
View file

@ -5,21 +5,28 @@ with GitLab and Jira.
# But... why? # But... why?
Mainly as a way to learn Rust to do a few things: Mainly as a way to learn _more_ Rust to do a few things better:
- Async (`tokio`) - Async with `tokio`
- CLIs (`clap` and `cliclack`) - Command-line interfaces (CLIs) with `clap` and `cliclack`
- TUIs (`ratatui`) - Terminal user interfaces (TUIs) `ratatui`
- Configuration (`config`) - Configuration with `config` and `keyring`
- Lazy-loading (`std::sync::OnceLock`) - Lazy-loading with `std::sync::OnceLock`
- Error handling (`color_eyre`) - User-facing error handling with `color_eyre`
- Logging (`tracing` and friends) - Logging with `tracing` and friends
- HTTP Clients (`reqwest` and friends) - HTTP clients with `reqwest` and friends
I expect to do many of these things wrong over the life of this project, which will hopefully help me do it more-right next time. I expect to do many of these things wrong over the life of this project, which
will hopefully help me do it more-right next time.
I co-maintain a Rust CLI at my current job, so these are all things I'm familiar
with, but always wanting to improve and try other ways of doing things to see
how they compare.
## But... why? ## But... why?
Deja-vu!
Yes, most companies would just setup the GitLab and Jira integration and call it Yes, most companies would just setup the GitLab and Jira integration and call it
a day. Everything would work nicely. a day. Everything would work nicely.