I love creating! It started with Lego as a little kid. Later I went on with (dis)assembling my first computer in the early 2000s. Then came the internet... Working remotely for 8 years :-)
I usually like having to use less tools, but I disagree for one reason: text editors are a very personal choice, plus this choice changes from time to time (I've been through many different text editors). So this will lock you and the entire team in one text editor.
Besides, you can also export your postman collection into one json file and put that in version control, no need for the payed plan. Other tools (insomnia) are able to import that => maybe it's compatible with VS code? That'll be nice.
I would not (easily) join a team, that forces me to use one particular text editor ;)
If you really want to cut tools, how about curl?
You can also auto-generate a OAS3 compliant API documentation, which you can use to, well, have a documentation, and also use it with curl. Or render it in the browser and build a little UI that allows you to fire requests from your browser. Serve that documentation file from your server, and also the frontenders can render the UI to make requests without having to run the API on their local machine.
Export Postman collection exposes you as the fact that you always need to do that (Postman don't auto save into your repo) and it's pretty boring.
The main point here is to be able to maintain it into a repo, without need another tool. It could be a shell script which make cURLs... but can be a pain in the @$$ to get all available features you'll find with REST Client, into a simple shell script.
I fully understand your point about the IDE. Really. In my case, I use during many years Emacs, then Sublime Text, and did not want to get a big IDE. But I opened VS Code and many others, and check the time saved ... based on our tech stack, currently VS Code seems to be the best choice.
I we would to have a final word, we could say that the better world is a .yml file to get a swagger
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I usually like having to use less tools, but I disagree for one reason: text editors are a very personal choice, plus this choice changes from time to time (I've been through many different text editors). So this will lock you and the entire team in one text editor.
Besides, you can also export your postman collection into one json file and put that in version control, no need for the payed plan. Other tools (insomnia) are able to import that => maybe it's compatible with VS code? That'll be nice.
I would not (easily) join a team, that forces me to use one particular text editor ;)
If you really want to cut tools, how about curl?
You can also auto-generate a OAS3 compliant API documentation, which you can use to, well, have a documentation, and also use it with curl. Or render it in the browser and build a little UI that allows you to fire requests from your browser. Serve that documentation file from your server, and also the frontenders can render the UI to make requests without having to run the API on their local machine.
I understand your point.
Export Postman collection exposes you as the fact that you always need to do that (Postman don't auto save into your repo) and it's pretty boring.
The main point here is to be able to maintain it into a repo, without need another tool. It could be a shell script which make cURLs... but can be a pain in the @$$ to get all available features you'll find with REST Client, into a simple shell script.
I fully understand your point about the IDE. Really. In my case, I use during many years Emacs, then Sublime Text, and did not want to get a big IDE. But I opened VS Code and many others, and check the time saved ... based on our tech stack, currently VS Code seems to be the best choice.
I we would to have a final word, we could say that the better world is a .yml file to get a swagger