I'm back on, what is VS code doing?
As of today, Oct, 4th, 2024 My vs code updated like an hour ago of posting this; the Explorer search function stopped working. I had previously posted a somewhat similar issue 3 months back. My issue back then was that when I pressed ctrl
+ f
the search bar only showed in the editor and not in the explorer. My VS code pops out the search bar on the explorer when I press ctrl
+ f
, so it's not the keyboard bindings as my issue from last time.
Now when I search for anything using the Search bar in the "explorer", all my folders in my explorer just disappear as if the search doesn't find anything. The "search" works if I just manually type the name of the folder in the explorer(not using the search bar). It is easer to just copy paste the name of the folder for the website I am working on so the search bar feature is somewhat important to me.
Anyone know if there's any settings change I need to make to fix this?
I've tried searching a bit on keyboard bindings to see if there's anything I can change and test, and also made some changes to my settings to anything pertaining to "explorer", "search", "find", "filter" but could not find anything that fixes the issue, Maybe I missed something.
I did test to see if the "editor" search was affected as well but everything works fine there.
I also tried the search on my personal projects folder since it consists of a much smaller stack of folders and when I tried search for a folder it did not load anything and the explorer showed blank but when I tried searching for a file, it seems to be searching for files but not folders, maybe this info can be of help?
I did try to search for files in my work folder but it's showing nothing, as the second Image I posted; Maybe it's just taking too long since there's a lot of folders it's sifting through; Still, this is not ideal.
Update:
It seem this issue was cause by the latest VS-Code update. A lot of people seem to be experiencing similar issues and the VS-Code team is looking into it. I downgraded to the previous v1.93 for the time being
It seem this issue was cause by the latest VS-Code update. The VS code team mentioned that they will be working on improving this in the following 2 months.
Github thread for reference: github.com/microsoft/vscode/issues/230714