Feature request: parse .http files/directories

[franksl]

Hi,
To avoid the use of non standard collection files I started using .http files that become very useful in neovim with the rest.nvim or kulala packages. I think it would be very useful to be able to launch ATAC by passing the path to a directory containing .http files and showing them as a collection.
Thanks,
Frank

[Julien-cpsn]

Hello,

For now, such a thing is not planned. Although, I am not closed to this idea. Can you please show me what your http file looks like?

Have a great day

Julien

[franksl]

Hi,
You can find some specifications here: https://learn.microsoft.com/en-us/aspnet/core/test/http-files?view=aspnetcore-8.0#http-file-syntax.
It is basically a plain text file where you put the kind of request, headers and payload in a way similar to how they are sent through the http protocol.
Frank

[ccoVeille]

tree-sitter-http is also a good source of thruth

[Julien-cpsn]

The import of those files is planned. Exporting toward this file format is also planned (and almost finished). So maybe you can use it this way:

• you import your .http files
• you use the collections as usual
• once finished, you export them to .http file format
• repeat

Is that ok for you?

(As said, the import/export of .http is not fully ready yet)

[franksl]

I think that would be good in order to keep my http files, thanks!

[rattrayalex]

I'd like to encourage this, both for .http files on disk, and with an arg, to compete with cURL.

I have come to like the VS Code REST Client much better than curl or other interactive api clients. It's so simple – I just edit the text of the raw http request!

However, sometimes I might want to run these requests from a CLI. In fact, in my case, I want to document various REST APIs with .http syntax, but also allow people to quickly try them from the CLI if they don't use an editor plugin.

For me, ideally, a request like this one would look like this:

atac http 'PATCH https://api.cloudflare.com/client/v4/zones/{{ZONE_ID}}/custom_hostnames/{{CUSTOM_HOSTNAME_ID}}
Content-Type: application/json
X-Auth-Email: {{CLOUDFLARE_EMAIL}}
X-Auth-Key: {{CLOUDFLARE_API_KEY}}

{
  "custom_origin_server": "origin2.example.com",
  "custom_origin_sni": "sni.example.com"
}
'