HN Reader

Interesting, a few questions: 1. How hard/easy is it to make responses dynamic, i.e. to use something from the request data like query/path param or a body to execute function instead of hardcoding the response 2. What's the main motivation for creating this tool? I feel like every programming language have similar tool already - WireMock for Java etc. Why should people switch?

> Making an existing API slow can be easily accomplished combining mock’s Base APIs and the delay option.

Ah, it's the "billable hours" variable.

It frustrates me no end when large commercial web sites fail to store state in URLs. It should be updated when the user clicks the 'submit' button of a page, especially when related to searching.

Some products have these fancy KQL style search parameters but if you forget to 'save the search' within the applications 'Save Search' facility, then when you duplicate a tab the search is lost.

It feels rude when sites ignore the UX improvement by not leveraging the power of URLs to store current state.

the name mock has also been used for the RPM build environment tool (https://github.com/rpm-software-management/mock)

Wonderful little tool! Something similar has been swirling aronud my head for a while. Thank you for sharing, it looks very useful.

Does it support Windows? I don’t see a Windows version on the GitHub releases page.

If you like lo-fi ways to attach cli commands to http end-points, you may also like:

- https://github.com/cablehead/http-nu or for POSIX - https://github.com/cablehead/http-sh

What a great tool! Writing simple scriptable mock apis all for the command line. Very easy to include commands straight into documentation.

How does this differ from swagger?