Enhancement: Navigate to field from Static typed field.

[Justin Julicher]

when you reference a field in code using e.g. ‘Contact.LastName’ and you navigate to declaration it goes to SObjectField type.

It would be more useful if it went to the definition of the field e.g. Contact LastName.

‌

‌

[Scott Wells]

Hah! Yeah, this has bugged me for a long time as well. It works that way because technically Contact.LastName is of type SObjectField, so adding that type of reference just makes other features such as chained code completions, reference resolution, type agreement, etc., work properly. However, you really do expect it to resolve to that named field when you navigate through it instead of to the more generic SObjectField. I'll take a look and see if I can change just the reference navigation aspect without breaking everything else that depends on that being linked to the correct data type for compilation purposes.

[Scott Wells]

I'm not seeing any easy way to do this. I've put in a query with the other plugin developers to see if there's just some feature of the plugin SDK that I'm missing that allows divergent reference resolution and navigation behavior.

[Scott Wells]

Figured it out. The change will be in the next build.

[Justin Julicher]

Awesome!

Once again you amaze me with your efficiency! Do you ever sleep?

Thanks

[Scott Wells]

Delivered in 2.1.6.1.

[Justin Julicher]

Hi @Scott Wells

I’ve just downloaded the latest version of IC and it seems this has been reverted? It goes to to the OST version not the field definition.

[Scott Wells]

Justin, I'm not aware of any changes in this area at all, but of course it could have happened as a side-effect of something else. Let me take a look and I'll see if/why it's not working.

[Scott Wells]

Hey, Justin. Which form isn't navigating properly for you? I have a series of tests that verify these various compile-time field constant patterns and I've just verified that they're all still navigating to the field in the OST SObject stub class which was the resolution of this bug.