Anyways, the folks have spoken, no need to double down. There are more than a dozen alternatives to it, and new ones are coming up.
I'm helping build a new one.
- Completely offline.
- Gives the ability to build reusable blocks (headers, query params, etc)
- Let's you document everything in Markdown.
- Imports your collections and cURLs.
* The text is tiny for my old eyes. I figured there's probably a setting for it and hit Cmd-, and found there's no settings UI whatsoever. No keyboard shortcut either it seems, and no help menu either, so no searching for "keyboard" with Shift-Cmd-/
* .void files may be markdown, but no markdown editor will recognize it as such. Maybe support .void.md as well. I also couldn't find any way to edit the markdown source of a .void file from voiden, which is a bit ironic for a tool that loudly advertises the markdown format as a central feature.
* Could there be a block that expands into the full URL of the request and parameters above it (or perhaps as args)? How about another that renders as a cURL command, which would cover POST/PUT/PATCH requests nicely too. My API documentation always has cURL request examples and I detest writing them by hand.
* While I'm suggesting blocks, one that renders the response headers/body to the preceding request would also be handy. It should support a placeholder response that gets replaced when the request is actually run (and perhaps a "save" button to persist it in the markdown). Responses get long, so maybe have a max-height for the block and make it scrollable
I'm actually really excited about Voiden and hope these can be addressed. It has a similar feel to Jetbrains' .http format, but an evolutionary leap beyond it. It also feels really raw and unfinished.