Evaluate re-introducing automatic code search routing for search literals
Following the changes in !212243 (merged), we removed the automatic redirection to the blobs (code) scope when users include code search literals (like blob:, filename:, path:, extension:) in their search queries. This was done to ensure the configured default search scope setting takes precedence.
However, this change may impact user experience for those who rely on automatic code search routing when using these literals.
Discussion Points
-
Usage Analysis: We need to gather statistics on how often users actually use code search literals in their queries to understand the impact of this change.
-
User Expectations: Should code search literals automatically route to code search, or should the configured default scope always take precedence?
-
Potential Solutions:
- Keep current behavior (configured default scope always wins)
- Re-introduce automatic routing for code literals as an override to default scope
- Make this behavior configurable via admin settings
- Provide better UI hints when code literals are detected but not searching in code scope
Context
The previous behavior automatically redirected searches containing code literals to the blobs scope, even if a different default scope was configured. The new behavior respects the configured default scope setting, but users must explicitly select the code scope when using code search literals.
Related: !212243 (merged), #567844