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
Create a folder test with the following folders in it:
normal
folder.js
folder.txt
folder.blabla
Then include contents and filter the type "folder" (in the "Types" field next to the depth slider). folder.js and folder.txt will not be indexed, but the other two will.
Excluding instead of including also gets it wrong (the opposite way).
Files are not detected as folders, even without an extension.
Presumably, a folder name ending with a "file extension" is heuristically treated as a file. This may make sense (certain packages like .app are basically folders, but are supposed to look like files to users), but there are valid reasons to have a "file extension" in a folder name.
In particular, such folder names are common with Javascript projects (think node.js). I personally came across this when I noticed that certain Javascript projects in my code folders were not being indexed.
The text was updated successfully, but these errors were encountered:
Create a folder
test
with the following folders in it:normal
folder.js
folder.txt
folder.blabla
Then include contents and filter the type "folder" (in the "Types" field next to the depth slider).
folder.js
andfolder.txt
will not be indexed, but the other two will.Presumably, a folder name ending with a "file extension" is heuristically treated as a file. This may make sense (certain packages like
.app
are basically folders, but are supposed to look like files to users), but there are valid reasons to have a "file extension" in a folder name.In particular, such folder names are common with Javascript projects (think
node.js
). I personally came across this when I noticed that certain Javascript projects in my code folders were not being indexed.The text was updated successfully, but these errors were encountered: