• The modal is not displayed, and a few exceptions get logged to the console while attempting to import a collection that follows the old format (without authorization and headers set at the root level).

  old-collections-format-exception.mov

• The collection entries synced to the personal workspace from local storage added while logged out do not persist. For instance, deleting any of them while being logged out affects the one in the personal workspace.

  personal-workspace-collections-affected-by-unauth-state.mov

• Authorization and headers set at the collection level go to the default state while importing collections into the team workspace.

  inconsistent-sate-collections-logged-in.mov

• There are exceptions thrown in the UI under headers while opting for the API key as the Authorization type and choosing the values to be supplied via headers. There is a similar issue that already exists for the request Authorization/Headers tabs, Ref. This might be happening since common components are involved. Please confirm.

  ui-exceptions-pass-by-headers.mov

• Is it intentional that the default Authorization type for a request not belonging to a collection is inherit? Shouldn't we keep the default type of None for those requests?

  default-auth-type-non-collection-request.mov

REST & GQL collections could not inherit from the ancestor levels and default to the authorization type of None.

Also, can you look into the failing tests?

• The currently active tab (REST & GQL) doesn't reflect changes made at the ancestor level. This applies to both headers and authorization.

  Screen.Recording.2023-12-13.at.1.07.18.PM.mov

• The modal is not displayed while importing GQL collections that follow the old format (without auth & headers) and there are errors logged to the console.