You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clarify regex vs literal text in search result messages (#1757)
* Initial plan
* Improve presentation of regex-based searches in agent mode
- Updated FindTextInFilesTool to indicate "regex" vs "text" in search messages
- Updated Claude grep tool formatter to show "Searched for regex"
- Added test for literal text search message format
- Updated existing test to match new regex message format
Co-authored-by: roblourens <323878+roblourens@users.noreply.github.com>
* Make regex/text keywords localizable via l10n
- Moved 'regex' and 'text' keywords inside l10n.t() calls
- This allows localization system to translate or keep terms as appropriate per language
- Addresses localization concern about whether 'regex' should be localized
Co-authored-by: roblourens <323878+roblourens@users.noreply.github.com>
* Refactor nested ternary operators into helper method
- Extract message generation logic into getResultMessage helper
- Improves code readability and maintainability
- All tests passing
Co-authored-by: roblourens <323878+roblourens@users.noreply.github.com>
* Update ChatSessionContentProvider test snapshot
- Updated snapshot to reflect new grep message format
- Changed from "Searched text for" to "Searched for regex"
- All tests now passing (8/8)
Co-authored-by: roblourens <323878+roblourens@users.noreply.github.com>
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: roblourens <323878+roblourens@users.noreply.github.com>
0 commit comments