feat: Add cURL Import Option In Dropdown Menu

[dCodes03]

Problem

Users had to discover the cURL import feature by accident (pasting into URL bar or via Import Data dialog, atleast I discovered it by accident). This made it hard to find and use.

Solution

Added a dedicated "cURL" option to the Create dropdown (Cmd+N) that opens a professional dialog for importing cURL commands.

feel free to close/ignore if unwanted

[dCodes03]

@gschier is this feature needed? What's your opinion here?

[macgbluedev]

Good idea! It's not easy the way to import a curl command 😉 I miss this options

[gschier]

I haven't had time to get to this one yet. It doesn't fit in the create menu (you're not creating a Curl request) like this PR has it, but I'm not sure of a better place for it yet.

[dCodes03]

hmm, maybe you're right, there should be something like "Import" I think

[dCodes03]

how about this one @gschier

[xzxiaoshan]

Importing curl is a great feature, as it is a cross-platform HTTP conversion method, and almost all similar tools provide curl export and import capabilities.

I was initially confused because Yaak did not seem to support curl import. Later, I found out that pasting directly into the URL worked, but I felt this interaction was too hidden. It wasn't until I came across this issue that I realized it was an excellent interactive feature.

I have been using the latest beta version, and the automatic clipboard read with an import prompt in the toolbar is fantastic. This interaction is really well-designed, and I am very grateful.

[xzxiaoshan]

@gschier

I noticed that Yaak does not have the issue submission feature open, so I will take this opportunity to provide a suggestion here. Although it is not suitable for submitting issues here, I apologize for that.

Regarding the "save to file" functionality for response results, it seems that compatibility is not fully addressed. The image below shows the file download feature, which outputs Content-Disposition according to the HTTP protocol, but the file storage could be improved.

Additionally, I believe that these headers should be displayed in a standardized camel case format, such as Content-Type instead of content-type.

---

content-disposition:

attachment; filename="%E4%BC%81%E4%B8%9A%E8%B4%B4%E6%81%AF%E8%B6%85%E9%99%90%E9%A2%84%E8%AD%A6.xlsx"; filename*=UTF-8''%E4%BC%81%E4%B8%9A%E8%B4%B4%E6%81%AF%E8%B6%85%E9%99%90%E9%A2%84%E8%AD%A6.xlsx

---