fix: user lists not refreshing after add, remove or role change - #9802
Merged
nishantmonu51 merged 1 commit intoAug 11, 2026
Merged
Conversation
The org users, invites and groups tables read through Orval's infinite queries, which are cached under an "infinite"-prefixed key. Every mutation invalidated only the plain key, and since TanStack matches keys by prefix, the invalidation never matched and nothing refetched: the tables only updated on a page reload. Add invalidateOrgMemberUsers, invalidateOrgInvites and invalidateOrgUsergroups, each invalidating both key variants, and route every call site through them.
AdityaHegde
approved these changes
Aug 11, 2026
nishantmonu51
deleted the
nishantmonu51/fix-org-user-list-not-refreshing
branch
August 11, 2026 15:47
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.
The org users, invites and groups tables read through Orval's infinite queries, which are cached under an
"infinite"-prefixed key (["infinite", "/v1/orgs/{org}/members", …]). Every mutation invalidated only the plain key (["/v1/orgs/{org}/members", …]). TanStack matches keys by prefix, so the leading"infinite"element made the match fail and nothing refetched — the tables only updated on a page reload.invalidateOrgMemberUsers,invalidateOrgInvitesandinvalidateOrgUsergroupstouser-management/utils.ts, each invalidating both key variants, and routed all 12 call sites through them: the add/remove/role-change dialogs, the groups tab, and the project-side invite forms.#9793moved that table to an infinite query but left the invalidations on the plain key.type: "all"from two project-side call sites. It is TanStack's default filter value, so it was a no-op.utils.spec.tscovers all three helpers: both key variants get invalidated, and another organization's cache does not.Checklist: