At the present time, the help text says that pressing 'd' deletes a request. It doesn't do that yet though.

• This feature would require some kind of confirmation popup

The key value add field is definitely not complete. You can't delete headers, and some of states are not working properly.

pt has a simple mechanism to make predefined HTTP requests. What would be really powerful if there was a way of defining 'arguments' to be interpolated into those requests.

For example:

What if fields could contain handlerbar syntax ({{ fieldName }}), and if they did - when you trigger a request a box pops up asking you to fill in the values for those fields.

Could also use this to generate --options on the command line

I'd quite like to set up some actual end to end tests that actually sets up some infrastructure, build the package, runs the actual command from a real shell, and calls real infrastructure to properly test it.

At present, when the 'request line' component receives a response, it puts the response body at the bottom of the card, fed through a syntax highlighting package. Still need to really think about the presentation of that component, because its a little rough and ready at the present time

Unfortunately, things like "waitFor" do not work with ink-testing-library so I have to rely on simple time delays. This is obviously a bit of an anti-pattern and has meant the tests are a bit flaky

When I started writing this package I was still exploring how 'ink' worked so wasn't really writing tests. I've retrospectively written a bunch of tests now I'm up to speed, but I'd like to get things to a place where its got 90% or more test coverage

The terminal based UX is actually quite cool imho, but you don't get a feel of it from the readme. I need to record a video of the tool in operation.