fix(grep): follow symlinks by default in ripgrep searches #7501
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
Fixes #7498 - Grep fails on symlinked directories
Changes
--followflag to grep tool for consistent symlink traversal--hiddenflag to grep tool for parity withRipgrep.search()follow?: booleanparameter toRipgrep.search()with defaulttruefor API consistency withRipgrep.files()Design Decision
Following VS Code's approach, symlinks are now followed by default since OpenCode is an IDE-like tool where users expect to find all their code regardless of filesystem structure. The
followparameter provides an escape hatch for users who need stricter behavior.Compliance
files()andsearch()now have consistent API for thefollowparameterfollowparameter explicitly communicates symlink-following behaviorNote for Maintainers
During review, we noticed that
grep.tsdoes not include--glob='!.git/*'whileRipgrep.search()does. This is a pre-existing inconsistency (not related to this PR). If you'd like us to add this for consistency, we're happy to update the PR.