VCST-5317: Hide locked organizations from the header org switcher - #192
Merged
Merged
Conversation
# Conflicts: # restapi/types/__init__.py # tests/e2e/frontend/test_account_menu_organizations.py
…ersions with the fix Customer 3.1024.0 and ProfileExperienceApiModule 3.1018.0 include the isLockedForCurrentUser field and the login-fallback fix this story's tests depend on; CI was still installing the older pinned versions. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
GraphQL and e2e regression tests verifying the header org switcher shows a locked organization as disabled (present in the list +
isLockedForCurrentUser: true) rather than excluded - covers VCST-5317 AC-1/2/3/5/6.REST lock/unlock organization-membership operations and a shared
lock_membershipfixture (available to e2e/graphql/restapi suites) to set up the locked state.REST regression test (
tests/restapi/platform/test_organization_login_fallback.py) for the related login fix in vc-module-customer#316: a password sign-in with a staleorganization_idmust still succeed once every organization the user belongs to is locked, instead of failing withuser_is_locked_in_organization.