Ignore .sfdx/orgs directory by default

[Aidan Harding]

I’m not sure if this is possible, so apologies if not!

The larger problem is that when I do a global search for something, I often get false hits from the .sfdx/orgs directory, when I actually wanted to just search all of my source. I can add the .sfdx/orgs to the excluded list on a per-project basis, which solves that.

But, there’s no global setting for that in IntelliJ (see https://youtrack.jetbrains.com/issue/IDEA-150784). So I have to do this for every single project.

I think the IC plugin probably generates the .idea/My-Project.iml so you might be able to do this for us in SFDX projects. I can’t see why anyone would object, and they can always remove the exclusion if they prefer.

[Scott Wells]

IC already adds exclusions for other subdirectories of the project's .sfdx, primarily to remove generated source files from evaluation. I'm curious about what is being found under .sfdx/orgs that is causing issues? I don't mind excluding it, but I haven't ever seen any issues with files under that directory.

[Aidan Harding]

The issue for me is in that global search.

If I’m looking for a class name where the built-in “Find Usages” doesn’t quite do it, I sometimes do a global search for class name.

The orgs directory contains the source-tracking info, so it can include references to the class name which are not interesting to my search. If there’s a long history, this can make global search useless until I exclude those directories.

For example, if I search for my class in one of my current projects, I get a hit in .sfdx/orgs/[e-mail]/maxRevision.json which is like this:

"ApexClass__MyClass": {
    "serverRevisionCounter": 67,
    "lastRetrievedFromServer": 67,
    "memberType": "ApexClass",
    "isNameObsolete": false
},

BTW, I’m not seeing any other exclusions in the .sfdx directory being automatically generated by IC

[Scott Wells]

Ah, okay. And as for other exclusions, it should offer to exclude .sfdx/tools/sobjects, .sfdx/typings, etc., but only when present. That will generally only occur if you've opened the same project in VS Code.

[Scott Wells]

Removing version: Unassigned (automated comment)