Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Request names/body getting shuffled around #213

Open
1 task done
fabian-qasolve opened this issue Jan 23, 2025 · 4 comments
Open
1 task done

[Bug]: Request names/body getting shuffled around #213

fabian-qasolve opened this issue Jan 23, 2025 · 4 comments
Labels
bug Something isn't working

Comments

@fabian-qasolve
Copy link

fabian-qasolve commented Jan 23, 2025

What happened?

The request names/body are shuffled around when I navigate back and forth from different requests/collections. I am not sure if it is the body or the request name on the left panel is getting shuffled.

Steps to reproduce?

1. Create some requests in 2 different collections
2. Switch back and forth between the requests and collections

What did you expect to happen?

I expected the request names/body to be intact

Platform

Windows

HTTPie Desktop version

2025.1.0

Relevant log output

Code of Conduct

  • I agree to follow this project's Code of Conduct
@fabian-qasolve fabian-qasolve added the bug Something isn't working label Jan 23, 2025
@antiflasher
Copy link
Contributor

I can't reproduce this behaviour. Can you please record a video demonstration?

@blaqshyd
Copy link

Just tried to reproduce the same behavior but couldn't, what I noticed is that switching between collections doesn't change the environment which I think is the right and intended behavior and I don't think that's what the OP was referring to.

@antiflasher
Copy link
Contributor

Just tried to reproduce the same behavior but couldn't, what I noticed is that switching between collections doesn't change the environment which I think is the right and intended behavior and I don't think that's what the OP was referring to.

Yes, the environment selector is applied to the entire space and is independent of the current collection.

Are there any use cases where a collection-dependent environment is more convenient for you?

@blaqshyd
Copy link

blaqshyd commented Feb 5, 2025

Yes, can something like how POSTMAN does it be included? Where you can pin one/more environment to a collection? That makes it easier to track even if you still have to change environment every time you select another collection. I switch between different collections a lot and it's a hassle to always select the environment every time especially when you've a lot of environment in the workspace. @antiflasher

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants