Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
When using the debugger and you fill in the 3 fields (namespace, workflow_id, and run_id), once the debugger is done running, you need to fill all 3 fields in again to get the history going. A bit repetitive. It would be nice if there was a history of requests that you can click to replay. This only really needs to be in memory. So when the VSCode instance is closed, the history is gone.
Same for files, if there was a list of files that were played and you can click to replay.
Additional context
On top of being a useful feature for the normal use-cases, the VSCode debugger won't allow you to restart a debugger if you have more than one debugger going. My engineers frequently have many projects going within the monolith we work on. When running through a workflow to do quick iteration, and using the VSCode debugger, if they get past a point they want to debug, they have to stop the debugger, re-enter the field(s), and start over.
Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
When using the debugger and you fill in the 3 fields (
namespace,workflow_id, andrun_id), once the debugger is done running, you need to fill all 3 fields in again to get the history going. A bit repetitive. It would be nice if there was a history of requests that you can click to replay. This only really needs to be in memory. So when the VSCode instance is closed, the history is gone.Same for files, if there was a list of files that were played and you can click to replay.
Additional context
On top of being a useful feature for the normal use-cases, the VSCode debugger won't allow you to restart a debugger if you have more than one debugger going. My engineers frequently have many projects going within the monolith we work on. When running through a workflow to do quick iteration, and using the VSCode debugger, if they get past a point they want to debug, they have to stop the debugger, re-enter the field(s), and start over.