Replies: 1 comment
-
The underlying problem is that my Two potential fixes (from that discussion) are to turn off the plugin, or to tell it how to define a project:
Clearly the defaults here aren't working well out of the box for this Javascript monorepo, so I left the issue open. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a Javascript/Typescript repository with a number of packages:
Obviously the root folder (
my-project/
) has the.git/
in it. There aren't any.git
folders anywhere else. But Telescope seems confused about what the root is:When I use the file finder (
<leader>f
), Telescope searches my entire repository (which is what I want), but the results falsely claim to be in the same package as the current file. For instance, If I'm looking atfileIAmLookingAt.js
and I search for "LookingFor", the Telescope match says:../src/FileIAmLookingFor.js
instead of../../packageC/src/FileIAmLookingFor.js
.When I do a string search (
<leader>st
), Telescope only searches within the current package (i.e. the package of the file in the current buffer). I get no hits outside of the current package. (There's no issue with reporting the relative path correctly.)What am I doing wrong here? Any guidance appreciated.
See equivalent issue (not getting any action so I'm trying my luck here).
Beta Was this translation helpful? Give feedback.
All reactions