ref: Use getApiURl() inside of static/app/components/*
#106897
Conversation
github-actions
bot
added
the
Scope: Frontend
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| }), | ||
| ] | ||
| : [''], | ||
| : ([''] as ApiQueryKey), |
There was a problem hiding this comment.
Missing email query parameter in member lookup
High Severity
The useMemberLookup hook's email lookup is missing the query filter parameter. The original code included {query: {query: \email:${email}`}}to filter members by email, but this was accidentally omitted during the refactor. The name lookup (lines 486-494) correctly preserves its query parameter{query: {query: name}}, but the email lookup now fetches all organization members unfiltered. This causes memberDataByEmail?.[0]` to return an arbitrary member rather than the one matching the specified email, breaking triage assignee matching functionality.
| const result = await fetchDataQuery<SyncReposResponse>(context); | ||
| const result = await fetchDataQuery<SyncReposResponse>( | ||
| context as unknown as QueryFunctionContext<ApiQueryKey, unknown> | ||
| ); |
There was a problem hiding this comment.
Cache invalidation uses mismatched query key format
Medium Severity
The cache invalidation in useSyncRepos still uses a raw string template literal for the repositories query key, but useInfiniteRepositories was updated to use getApiUrl() for its query key. This mismatch means queryClient.invalidateQueries() won't find the cached query because the keys are constructed differently. After a successful repository sync, the stale repository list won't be refreshed because the invalidation silently fails to match.
See: https://gist.github.com/ryan953/af5458fa4f89ae42cc19e8ea266b7e9a