mantono / fire

Terminal HTTP request mananger (like Postman and Insomnia)

☕ I am a software developer that loves coffee and bicycling, with an affection for state machines, event sourcing and functional programming

fire's Issues

Try to remove tokio as dependency

This application has no real need for an async runtime, so tokio should not be needed as a dependency, but right now it is a (transitive) dependency anyway. Investigate if tokio (and other dependencies) can be removed by either disabling some features that are enabled right now or by replacing some dependencies.

Support interactive requests

Support requests in interactive mode (-i, --interactive). When doing a request in interactive mode, a value for a template variable will not cause an error, instead the user will be asked to input a value. This will done in turn for each and everyone of the missing values (if several) until there are values present so a proper request can be done.

Before executing the request with the given values, a summary of the request will be shown so a final confirmation can be given. This implies -r + -H.

Add substitute "{{uuid()}}" with a generated UUID

Sometimes requests needs to contain certain properties that can/should/must contain unique values on each request, like correlation IDs or idempotence keys. But it would be tiresome to manually regenerate and update these values before each request.

By adding a template variable that could indicate that a UUID should be generated instead of the placeholder, there would be no need to manually update it for each request. Syntax should preferrably something that is not too akward to read/write but neither something that is too likely to have a collision with an actual environment variable (and in case of collision, the user supplied environment variable should take precedence).

Exact format to use needs some additional consideration. Some examples might be;

• {{UUID()}}
• {{uuid()}}
• {{_UUID}}
• {{_uuid}}

There might also be similar use cases when for example a current date / time / timestamp might need to be provided as a part of a request.

This may be included as an optional feature since it would have an additional dependency on a crate for uuid generation.

RUSTSEC-2022-0048: xml-rs is Unmaintained

xml-rs is Unmaintained

Details
Status	unmaintained
Package	xml-rs
Version	0.8.4
URL	https://github.com/netvl/xml-rs/issues
Date	2022-01-26

xml-rs is a XML parser has open issues around parsing including integer
overflows / panics that may or may not be an issue with untrusted data.

Together with these open issues with Unmaintained status xml-rs
may or may not be suited to parse untrusted data.

Alternatives

• quick-xml

See advisory page for additional details.

Consider ureq

Look into replacing reqwest with ureq for HTTP request. While reqwest is a perfectly fine HTTP client, ureq's focus on simplicity and only supporting blocking requests fits the use case for this application better.

Remove dependency on git

Remove dependency git2, which is only used for one single thing, which can be rewritten by hand, or possibly use an existing crate for same functionality.

Add syntax hilighting of response body

Consider using https://github.com/trishume/syntect