lws-mock-response
Middleware adding mock responses to lws.
Imagine the network is down or you're working offline, proxied requests to https://internal-service.local/api/users/1
would fail. In this case, Mock Responses can fill the gap. Mocks are defined in a module which can be reused between projects.
Trivial example - respond to a request for /rivers
with some JSON. Save the following Javascript in a file named example-mocks.js
.
{ return route: '/rivers' responses: response: type: 'json' body: name: 'Volga' drainsInto: 'Caspian Sea' name: 'Danube' drainsInto: 'Black Sea' name: 'Ural' drainsInto: 'Caspian Sea' name: 'Dnieper' drainsInto: 'Black Sea' }
Launch ws
passing in your mocks module.
$ ws --mocks example-mocks.jsServing at http://mbp.local:8000, http://127.0.0.1:8000, http://192.168.0.100:8000
GET your rivers.
$ curl http://127.0.0.1:8000/rivers[ , , , ]
Adds the following options to lws.
--mocks file ... One or more modules exporting Mock Responses.
See the tutorials for more information and examples about mock responses.
© 2016-20 Lloyd Brookes <75pound@gmail.com>.