I am impressed with the behavior of dot-http and thanks to the team for building a wonderful tool.
Here are a few use cases where the product did not fit in and workarounds were used.
|---/httpfiles
|--request-01.http
|--request-02.http
|--request-03.http
When a directory tree like above has multiple HTTP request files. The expected directory argument fails
$ dot-http httpfiles/*
error: Found argument 'httpfiles/request-01.http' which wasn't expected, or isn't valid in this context
USAGE:
dot-http [OPTIONS] <FILE>
For more information try --help
An alternative solution was applied to handle the problem but would have been better with proper command-line integrations
Applied alternate solution
$ for FILE in httpfiles/*; do dot-http -n http-client.env.json $FILE; done
I am impressed with the behavior of dot-http and thanks to the team for building a wonderful tool.
Here are a few use cases where the product did not fit in and workarounds were used.
When a directory tree like above has multiple HTTP request files. The expected directory argument fails
An alternative solution was applied to handle the problem but would have been better with proper command-line integrations
Applied alternate solution