Apex Go To Declaration seems to prefer OST

[Xander Victory]

Reproduction:

1. Create new project (I’m using sfdx based with Sandbox org)
2. Connect to existing org with custom Apex classes
3. Let it generate the OST
4. Download all Apex classes (non namespaced)
5. Go to some apex code
6. Attempt to go to definition on a method that is present in both the OST & a local copy of (from step 4)
7. Taken to the OST version (no method body)

Workaround is naturally to regenerate the OST

[Scott Wells]

Interestingly I have a change for the next release that may address this. If not, I'll certainly look into it further because obviously that can lead to confusion at best, but likely issue with features that depend on finding the right source as well.

[Xander Victory]

Sadly I’ve just seen this reoccur (noticed because a method was showing as unused) on a separate org

IC2 2.1.1.8

[Xander Victory]

updating version tag

[Scott Wells]

Thanks for letting me know. I'll see if I can find whatever is still causing this.

[Scott Wells]

Issue tracker grooming. I've tried to address this a few different times and it kept coming back up. If you're still seeing it and especially if you have reliable reproduction steps, please let me know.