11–18 of 18 posts
have you checked this https://github.com/federicotdn/verb . Its emacs package and i am able to write and test api's with text files.
With Lama2, my approach is to separate the language from the various editor extensions. Keep the language simple/lean and then build extensions/integrations to different text editors & IDEs on top of the core.
Does this support request chaining?
I do not want to import xpath/jsonpath syntax as is.
My goal is: if a new intern joins my team, I don't want to send them 3 reference docs (for lama2, xpath and jsonpath) just so they understand what's going on with APIs :)
So I am still musing of ways to get some sort of chaining, without complicating the syntax. Implementation is not the problem, but the right level of complexity (a.k.a does this pass the "intern test"?)
How does this compare to https://github.com/Huachao/vscode-restclient
If I add an intern into my team, I want them to "get" what's going on with APIs without many reference docs. So it has to pass real "intern tests".
Second difference is: I want to keep the "language" and "extension" utterly separate. In fact, I want `l2` support in multiple editors; VSCode is just a start.
Third, I have a rudimentary Postman import, which preserves original hierarchy/organization. My focus is to get the basic features of Postman with similar ease of use, on top of a lightweight UI. (maybe 20% of Postman's features; not more)
The JetBrains IDEs have a similar feature (text based REST client). It’s got a ways to go but has also come a long way, you can see from the patterns in release notes it’s a focus for JetBrains. I can’t wait for it to mature. For this purpose, text configs >>> a GUI like Postman. IMHO even more so when tightly integrated with the IDE/debugger/etc.
[1]: https://blog.jetbrains.com/idea/2022/12/http-client-cli-run-...
One thing I feel we do really well is chaining of HTTP requests. And we have plugins for IntelliJ[3] and Visual Studio Code[4].
Maintaining a tool like this as open-source is a big effort, all the best !
[1] https://github.com/karatelabs/karate
[2] https://www.karatelabs.io/first-class-citizens
[3] https://plugins.jetbrains.com/plugin/19232-karate
[4] https://marketplace.visualstudio.com/items?itemName=karatela...
Congrats on the launch ! I'm the lead dev of Karate[1] and was wondering if you had come across it. I strongly agree with you that collaboration should be via Git and the IDE[2] and that traditional solutions fall short. I hope Karate's syntax passes your "memory friendly" test :) We get regular feedback is that it is easy to read and even non-programmers can pick it up. One thing I feel we do really well is chaining…
Plugins - both the extensions look great!
Thanks for your thoughtful response with context.