fix(search): find bare filenames throughout the workspace - #2581
Merged
Merged
Conversation
Contributor
🖥️ PR preview
|
This branch was previously deployed
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
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.
find_filescurrently searches only root-level files for patterns such aspackage.jsonand*.ts, so agents miss nested packages and source files.Match basename-only patterns at every depth while keeping directory-qualified globs such as
src/*.tsscoped as before. Regression tests cover both behaviors.Validation:
pnpm run check. The nested-filename regression fails on current main. Search plumbing only; no DOM or layout changes.