Maybe onsider making it a PWA?
If it's client side only it would probably benefit from being installable and kept around via cache for offline use
Since I didnt get a popup to install and didn't see a manifest I assume this isn't in the plans, Maybe you have another solution for it like a web wrapper?
1. hurl.dev seems to do a lot more, with a focus on testing/CI/CD. I am focusing more on simplifying the request/response flow alone. I primarily care about interactive usage. IMHO, tests and CI/CD are better done through project languages, such as Python.
2. hurl.dev seems to focus less on team/collaboration aspect. For me, the first and foremost usecase is onboarding new teammates, ability to link APIs in code reviews, finding diffs in API, etc. Ease of use is paramount. So, I have developed a VSCode extension (https://marketplace.visualstudio.com/items?itemName=hexmos.L...), and want to focus on developing integrations with various other editors as well.
3. Another agenda I have is to develop good documentation and communication around a Plain-Text based API workflow for teams. I believe explicitly explaining how a Plain-Text + Editor GUI workflow can remove the need for expensive solutions is an important point.
4. I believe the syntax for hurl.dev is not exactly "memory-friendly". Example:
HTTP/1.1 200
[Captures]
csrf_token: xpath
"string(//meta[@name='_csrf_token']/@content)"
# Do login!
POST https://example.org/login?user=toto&password=1234
X-CSRF-TOKEN: {{csrf_token}}
I am resolved to keep the syntax simple/readable first and foremost so that I can onboard new people into the language real fast, with less dependency on repeatedly referring to documentation.
5. Lama2 is implemented in Golang (while hurl is in rust).
Hi, maintainer of Hurl here [1]! We try to make a really simple syntax while enabling passing data between requests. I find Hurl syntax clean, but beauty seems to be in the eye of the beholder... Good luck with Lama2!
Apologies if it came across as an attack -- emphasis on "I believe" :)
In text markup as well, there exists a wide range of options to choose from. MD/WikiText/AsciiDoc/reST/BBCode etc. Each seems to be optimised for slightly different contexts.
No offense! I really think there’s a strong need for a « Mardowned » HTTP format, for documentation, tests etc… Lots of good solutions, Lama2 included.
The abstraction is provide better UX. Anyone will have to write stuff over telnet to provide chained requests, variables, assertions, etc. Once you do that, you basically get a reimplementation of hurl.
Curl is a good tool to familiarize yourself with, but I've written test with curl and bash it is very cumbersome this is another level of awesomeness for that. If all you are going to do is connect to a server with some json, then curl is ok, I agree that nc/telnet/socat might be a bit extreme.
Hurl is not enough for some of the tests I want to write, i.e. testing sending a 50MB file, or dynamic content.
- First charge needs a AFA and it will setup a mandate
- Subsequent charges will use that mandate and work without 2FA
- Cardholders need to be notified in advance of a debit and be given an option to cancel
What's breaking now for most services is handling the third part
I built https://utils.foo last week. Client side only + ads free. Idea is to keep adding more utils to it, but keep it client side only.