Note - This post is intended to look for feedback in a tool that solves a problem we have been seeing (around API clients not supporting Python) - and hopefully help Python folks (like it helped us when building it).
So, a bit of a backstory - Something I noticed while we were building our internal tool for API testing: A lot of developer tools assume JavaScript scripting by default. API clients are a good example of this.
scripting = JavaScript
And yes it might not be always a huge problem, but it adds constant friction.
Eventually we realized the real issue was not just JavaScript. The issue was and is that many tools force a single language.
So when we started building our own API client (link below), we decided to approach scripting differently: Pre-request and post-request scripts support multiple languages and runs on real interpreters, not a limited sandbox like most Clients do.
So we built this to support Python and JS from day 1 and now releasing shell script + more coming (perhaps Go would be the next??)
The idea is simple: Your API tool should adapt to your stack, not the other way around.
Some developers think in JS, some in Python, some in Go or Rust.
The tool shouldn’t care.
Q: Would you actually use Python for request automation inside an API client, or do you prefer handling that logic outside the tool?
Repo: https://github.com/VoidenHQ/voiden
Yes, I would prefer Python over JS, but both are on the very bottom of what I would like to use or what is even preferable for my IRL projects at work.
cool - what would then be on the very top of what you would like to use? :)
I would prefer Java, bash or for my projects at work PHP, but I understand some ppl prefer JS, because their app will use JS to use the API.
you can keep an eyes on our github issues cause these languages will come soon!