languagetool-code-comments
ht
| languagetool-code-comments | ht | |
|---|---|---|
| 2 | 39 | |
| 31 | 4,753 | |
| - | - | |
| 7.6 | 9.0 | |
| 3 months ago | 3 days ago | |
| Rust | Rust | |
| MIT License | 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.
languagetool-code-comments
-
LanguageTool-Rust v2 releases 🎉: using LanguageTool grammar checker with Rust
languagetool-code-comments: uses LTRS to check for grammar errors within code comments
- [Release] languagetool-code-comments - Integrates the LanguageTool API to parse, spell check, and correct the grammar of your code comments!
ht
-
Curl is now a CVE Numbering Authority
No need to use curl, make HTTP requests great again with https://github.com/ducaale/xh
-
Why people in Google hate Go?
Except when you actually enjoy things being fast. For example, HTTPie easily adds 0.5-1s delay to every request because it's written in Python, especially on the first invocation. xh (https://github.com/ducaale/xh), on the other hand, starts immediately because it's written in Rust. I very much like this trend.
-
HTTPie Desktop: cross-platform API testing client for humans
HTTPie is great and was a big improvement for me over cURL.
However, I ended up switching to xh[1] as it's significantly faster and I prefer its output.
https://github.com/ducaale/xh
-
Tell HN: Postman just wiped all my stuff
No, but unless portability is a concern or you're massively familiar with curl, you might want to consider xh. It's much more intuitive.
https://github.com/ducaale/xh
-
🐚🦀Comandos shell reescritos em Rust
xh
- Insomnia REST client now requires an account
-
The curl-wget Venn diagram
wget on the other hand, automatically converts the ñ to UTF-8 hex and resolves the link perfectly.
I've searched the curl manpage and couldn't find a way to solve this. Please help.
I'm having to use `xh --curl` [1] to "fix" the links before I pass them to curl.
[1] https://github.com/ducaale/xh
-
Get better with Vim one tip at a time
Very nice, you should add xh to the User-Agents though.
-
I Could Rewrite Curl
While not a rewrite - one recent tool for making http requests which i quite enjoy is:
https://github.com/ducaale/xh
It's basically python httpie rewritten in rust. my only gripe is that i keep forgetting that it exists - and that "xh" is for http and "xhs" is for https.
So i frequently end up with curl anyway:)
- xh: Friendly and fast tool for sending HTTP requests (HTTPie in Rust)
What are some alternatives?
page - Use neovim as pager
rustdesk - An open-source remote desktop, and alternative to TeamViewer.
moveline.nvim - Neovim plugin for moving lines up and down
htmlq - Like jq, but for HTML.
vale - :pencil: A markup-aware linter for prose built with speed and extensibility in mind.
httpie - 🥧 HTTPie CLI — modern, user-friendly command-line HTTP client for the API era. JSON support, colors, sessions, downloads, plugins & more.
nvim-send - Essentially "nvim --remote-expr <expr>" / "nvim --remote-send <keys>" or "nvr --nostart --remote-send <keys>" in Rust
gitoxide - An idiomatic, lean, fast & safe pure Rust implementation of Git
languagetool-rust - LanguageTool API in Rust
tty-share - Share your linux or osx terminal over the Internet.
watchexec - Executes commands in response to file modifications
thgtoa - The Hitchhiker’s Guide to Online Anonymity