feat(cmdk): surface Client Keys (DSN) when searching "SENTRY_DSN"#116883
Merged
Conversation
The command palette matches queries against an action's label, details, and keywords using fzf, which requires every query character to appear as a subsequence of a candidate. Typing the SDK env var name SENTRY_DSN failed to surface Client Keys (DSN) because no keyword contained an underscore, so the '_' broke the match — even though plain 'dsn' worked. Add SENTRY_DSN as a keyword on both the project-settings nav item and the current-project quick shortcut so it behaves like 'dsn'.
Add a 'Sentry DSN' keyword alongside 'SENTRY_DSN' so the natural space-separated phrasing surfaces Client Keys (DSN) too, since fzf's subsequence matching treats the space and underscore as distinct characters.
github-actions
Bot
added
the
Scope: Frontend
JonasBa
approved these changes
Jun 4, 2026
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
3 participants
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.
Summary
Typing
SENTRY_DSN(orSentry DSN) into the CMD-K command palette now surfaces Client Keys (DSN), just like typingdsnalready does.SENTRY_DSNis the SDK environment variable developers set to configure their DSN, so it's a natural thing to search for when looking for that page — but it returned nothing before.Why it didn't work
The palette scores each action by fuzzy-matching the query against its
label,details, andkeywordsviafzf(commandPalette.tsx).fzfis a strict subsequence matcher: every character of the query must appear, in order, in a candidate string. Plaindsnworked becausedsnis a keyword on the Client Keys actions.SENTRY_DSNfailed because none of those keywords contained an underscore, so the_alone broke the match.Change
Add
SENTRY_DSNand the spacedSentry DSNform as keywords in the two places that surface Client Keys (DSN):navigationConfiguration.tsx— the canonical "Client Keys (DSN)" project-settings nav item. This feeds both the CMD-K project-settings group and the regular settings search, so both now respond.commandPaletteGlobalActions.tsx— the current-project quick shortcut ("Client Keys (DSN) - "), so on a project page you get the same parity withdsn.The two keyword forms together cover the env-var (
sentry_dsn), spaced (sentry dsn), and no-separator (sentrydsn) inputs. The tokens are left unwrapped (nott()) since they're fixed config/product strings, not translatable prose — matching howproject.slugis already used in those arrays.Test plan
SENTRY_DSNandsentry dsncases to the existing search-recallit.eachincommandPaletteGlobalActions.spec.tsx.commandPaletteGlobalActions.spec.tsx→ 17/17 pass.lint:json all changed files → clean.https://claude.ai/code/session_01PMrmgRxmMfZF3J7XyhF5yG
Generated by Claude Code