The current version always recreate records on replay (Except OIDs, although not 100% sure).
Have a configurable flag to control this behavior: a boolean that determines if the records are recreated on each replay or only during first.
Also, add an API to clear the record. The goal is to be able to make DDD seamlessly within Seeker, if possible.
Just a random idea (Need to be refined): Additionally, add an option to change the value of variable in the current context of the debugged program (or in case of message sends, to change the sender or the arguments about to be sent. (no need to modify the return of a method), and to override the returned value of a return expression (when inside the returning method)
The current version always recreate records on replay (Except OIDs, although not 100% sure). Have a configurable flag to control this behavior: a boolean that determines if the records are recreated on each replay or only during first. Also, add an API to clear the record. The goal is to be able to make DDD seamlessly within Seeker, if possible.
Just a random idea (Need to be refined): Additionally, add an option to change the value of variable in the current context of the debugged program (or in case of message sends, to change the sender or the arguments about to be sent. (no need to modify the return of a method), and to override the returned value of a return expression (when inside the returning method)