Kong / Kong/insomnia

Not deleting requests from other branches while switching them

Open
#6,016 3 comments 0 reactions 0 assignees View on GitHub
B-bug S-unverified
Dominant language
TypeScript
Stars
40k
Forks
2.4k
Avg merge
2d 13h
Merged PRs (30d)
61

Description

### Expected Behavior

I would expect to hide/delete requests and requests group, after switching the branch

### Actual Behavior

While changing a branches in debug page, the request groups and requests are not hiding/deleting and they are still there and those can be commit and push into branch

### Reproduction Steps

1. created requests
![image](https://github.com/Kong/insomnia/assets/120559020/543ec625-e599-44c9-90e0-5a12c0642c4f)
2. create a new branch out of it
3. in new branch edit them, add, delete, rename
4. commit, push
![image](https://github.com/Kong/insomnia/assets/120559020/af08fb9c-67b9-47ec-88b2-f6112ade4379)
5. go back to branch before
![image](https://github.com/Kong/insomnia/assets/120559020/543ec625-e599-44c9-90e0-5a12c0642c4f)
6. go back to newly created branch
![image](https://github.com/Kong/insomnia/assets/120559020/1a732032-c3b8-402f-9336-b6e89cb0f70f)

### Is there an existing issue for this?

- [X] I have searched the [issue tracker](https://www.github.com/Kong/insomnia/issues) for this problem.

### Additional Information

_No response_

### Insomnia Version

2023.2.2

### What operating system are you using?

Windows

### Operating System Version

Windows 11 version 22621.1702

### Installation method

exe

### Last Known Working Insomnia version

_No response_

Contributor guide

Open the contributing guide

Research direction

Start in the debug page's branch-switching flow and reproduce the sequence of creating a branch, editing requests, committing, switching back, and returning to the new branch. Trace how request groups and requests are loaded or cleared during each switch. Done means requests from another branch are no longer visible or commit-able after switching, with coverage for the reported Windows scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.