Repository navigation
Proton Pass: show vaults before sharing and guard member refresh - #3
Merged
bst1n merged 1 commit intoOct 10, 2026
Conversation
2 of 5 tasks
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
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.
List Vaults currently waits for optional sharing/member lookups before showing already-fetched vaults and item counts. A sharing refresh also reuses an adapter across the role lookup and subsequent member commands, allowing new commands to launch after browser login has started.
Show and cache the primary listing first, then add sharing details when ready using the existing latest-request and save-order guards. Acquire the guarded adapter before each member command, including commands queued behind earlier member requests. Existing sharing failure fallback, complete-listing cache rules, and contributor login-check fixes remain intact.
This is a narrow follow-up against the current branch for raycast/extensions#31877, addressing the two remaining outside-diff findings. It is based on
f0a21c6156f18eba97e28493a360f6c19f0ad189; it does not change the fixes ine687d611orf0a21c61. Please integrate into the existing upstream PR for Raycast review/publication.Validation:
git diff --checkpass.Prepared with Codex; draft for human review.