I’ve found tools like Charles really useful for understanding what’s happening on the wire. When I need something more repeatable (tests, offline work), I usually reach for a mock server instead. I ended up building a small one for my own use and later open-sourced it:
Great article. In addition, updating your mocking code can often be time-consuming. To try to make this easier, I built mock[1], which streamlines the process of setting up mock services for testing.
It's also possible create an HTTP service that acts as a wrapper to yt-dlp with just a few lines of shell, I created this example in the following link:
Swagger is a tool for API design and documentation.
Mock on the other hand is an actual API creation utility with which you can define endpoints, execute some logic for each endpoint and then return some data to the client. There are other similar features which are covered in the user guide.
Mock is not:
- A tool for API Specs or documentation
- A GUI tool.
I admit explaining the usefulness of this tool is not the easiest thing.
That's true, it's not a very unique name. I started building it, but only months later I thought of making it public. And then never thought of renaming it.
https://dhuan.github.io/mock/latest/examples.html
reply