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?
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.
12 comments
[ 2.3 ms ] story [ 16.4 ms ] threadAh, it's the "billable hours" variable.
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.
- https://github.com/cablehead/http-nu or for POSIX - https://github.com/cablehead/http-sh