launchiamenterprise / keyrunner

KeyRunner: A secure, codeless VS Code extension for API testing & Designing. Features include data encryption at rest, sensitive data masking, and the innovative Playground for chaining API requests without coding
https://keyrunner.app
MIT License
15 stars 1 forks source link

The "History" feature (from the left nav) does not seem to work #86

Closed frank-duq closed 1 month ago

frank-duq commented 1 month ago

Describe the bug After executing a few requests, the History panel remains empty, not showing any executed requests, and instead, telling you:

"Your request history is currently empty As you make API requests, they'll be stored here for easy reference and re-execution. Start making requests to populate your history!"

To Reproduce Steps to reproduce the behavior:

  1. Create and Submit a Request
  2. Click on the "History" tab from the left nav bar
  3. See that the History panel remains empty, not showing your expected executed request.

Expected behavior All executed requests are displayed in the History panel as expected (with the possibility to 'clear' them through some button..)

Screenshots Screenshot 2024-10-18 at 11 57 02 AM

Desktop (please complete the following information):

launchiamenterprise commented 1 month ago

@frank-duq Have you tried switching the workspace after submitting the request? We tested this across multiple workspaces and could see the history without any issues.

Could you please check in this folder (C:\Users{{user}}\AppData\Roaming\Code\User\globalStorage\keyrunner-lite-by-liam) and confirm if there is a file named "previous_requests"?

image
frank-duq commented 1 month ago

The "previous_requests.json" is indeed empty:

Screenshot 2024-10-18 at 1 02 29 PM

And to answer your question regarding if I tried switching the workspace, answer is no, I haven't played with that feature yet, so it is set to "Default" since day one, and definitely ok with it, in the sense that, I don't have the need [yet] to switch workspaces and isolate my collections in different workspaces (e.g. I'll be isolating my different use cases in different collections, yes, but all that inside the single "Default" workspace).

launchiamenterprise commented 1 month ago

@frank-duq Please update to v1.0.70. This issue should be fixed now. Let us know if the issue still persists.

frank-duq commented 1 month ago

Confirmed, it's working now!

The only thing I would add to it, is the ability to CLEAR any folder in there, but yeah, that's a feature request, current issue can be closed, tx.

launchiamenterprise commented 1 month ago

Thanks for raising the issue. This was an edge case that we missed and not sure how this scenario came up:) . Clearing folders and a trash screen for retrieval of any deleted requests/collections/history is in our pipeline. We will keep you posted.