[Bug]: Authorization Conflict: New Collection Inheriting API Key from Original Collection Instead of Using BasicAuth

[amirhoseinjfri]

What happened?

I set up an inherited API key for my first collection and applied it to all sub-requests, which worked perfectly. Later, I created a new collection with BasicAuth and changed its sub-requests to use "Inherited" authorization. However, when I tried making requests, I received a "Not Authorized" error. On inspecting the request headers, I found that the new collection was incorrectly inheriting the API key from the first collection instead of using its intended BasicAuth.

i hope i explained well, thanks

Steps to reproduce?

1. Open the app.
2. Create a new collection (Collection A).
3. Create an API key for Collection A and set it as "Inherited."
4. Apply the inherited API key to all sub-requests of Collection A.
5. Verify that all sub-requests of Collection A work as expected.
6. Create a second collection (Collection B) and set it up with BasicAuth.
7. Change the authorization for all sub-requests of Collection B to "Inherited."
8. Attempt to send a request with Collection B and observe the "Not Authorized" error message.
9. Check the request headers and see that Collection B is inheriting the API key from Collection A instead of the intended BasicAuth.

What did you expect to happen?

not having this issue i guess!

Platform

Windows

HTTPie Desktop version

2024.1.2.0

Relevant log output

No response

Code of Conduct

• [x] I agree to follow this project's Code of Conduct