Search looks inside Typescript files even with Source Files disabled

[mlevison]

What a mouthful. I will try do describe this more carefully. My filesearch is configured as illustrated:

 

yet when I search inside files, I get noise from massive number of node js/ts files:

What is the most elegant way of excluding these? (With enough digging I’m sure there is a way to exclude …/node_modules/… - however that will only work from the current project. For better and definitely worse, there will be more node js projects.

[vitor]

Yes, indeed node_modules are a pain. See Removing node_modules files from Alfred's results for ways to ignore them.

[mlevison]

Appreciate the quick answer reading:

Quote

• Remove the whole node projects folder from Alfred's search scope.
• Create a File Filter workflow search that doesn't include those folders.

The two approaches above are only additive. Both allow you to define what to search but don't provide a way to remove something at a lower level. For instance, I want to search: /Users/marklevison/Documents/GitHub/Astro/mlevison but not /Users/marklevison/Documents/GitHub/Astro/mlevison/node_modules.

 

For now, I'm confused. Since the `alfred:ignore` is implemented by the Alfred team, why not make the same functionality part of the preferences pane? My concern is that I either implement this using the tag or the Spotlight. In six months after I forget about this post. How will I remember the magic involved?

[vitor]

10 minutes ago, mlevison said:

Since the `alfred:ignore` is implemented by the Alfred team

 

It’s just a normal Finder tag that is told to be ignored when programatically querying the Spotlight database. There’s nothing magic to it and no extra implementation.

 

10 minutes ago, mlevison said:

In six months after I forget about this post. How will I remember the magic involved?

 

The workflow linked there also shows files with that tag and can remove it. And if you’re not finding files you need and report that, you’ll be directed to the troubleshooting steps, and the troubleshooter finds that stuff. Every change you make on a computer is something you can forget and may need to remember later, which is why documentation is important (and exists for this).