You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
import{Server}from'kakapo';constserver=newServer();server.startRecording();// Later in your app you do as many requests as you want$.get('/users')$.post('/user',{name: 'hector'});// Later you stop recordingserver.stopRecording();
So, basically what's gonna happen is, Kakapo will save all the request that has been dispatched while he was recording, the url, the response... all the important info in order to re-create the request later.
Later Kakapo will store internally all that info and automatically will handle the requests and responses the same way as your real backend did it.
It will be also cool something like
constrecordedData=server.getRecordedData();//Later in the future...constotherServer=newServer();otherServer.loadData(recordedData);
This will basically return an object or a serialized string which represents all the events that has been recordered and you can load them in the future in other apps, or other sessions or different servers, etc, etc
The text was updated successfully, but these errors were encountered:
@devlucky/kakapo-core Take a look guys, I think it will be also interesting on the Swift side, and not so difficult to implement, of course some api might change depending on the language, etc...
Imagine something like this:
So, basically what's gonna happen is, Kakapo will save all the request that has been dispatched while he was recording, the url, the response... all the important info in order to re-create the request later.
Later Kakapo will store internally all that info and automatically will handle the requests and responses the same way as your real backend did it.
It will be also cool something like
This will basically return an object or a serialized string which represents all the events that has been recordered and you can load them in the future in other apps, or other sessions or different servers, etc, etc
The text was updated successfully, but these errors were encountered: