Conflict with field naming in SObjects and namespaces

[Igor Petrovych]

If there's a managed package installed and you create a field of same name as in managed package - all the navigation and references resolve to managed package. For instance, if there are 2 fields on the SObject - Namespace__Lot__c and Lot__c, the 2nd one is not visible to Illuminated Cloud when referencing and navigating.

[Scott Wells]

Thanks for reporting, Igor. I'll take a look for one of the next few builds. I'll let you know if I need additional detail to reproduce it, but hopefully what you've provided in the description will be sufficient.

[Scott Wells]

Okay, I've implemented this. It was more complex than I'd have thought, but it's a really good change to make. It changes the way that namespaced fields are rendered into the OST--now they include their namespaces explicitly--and of course there were corresponding changes required to the way that references are injected, code completions are displayed, etc. I'm actually very happy with the change as it resolved a few other issues that had been lingering in this area. However, given the complexity of the change, I'm going to burn it in myself for a bit (likely a few days to a week) to avoid potential issues for the wider user base by releasing early.

I'm happy to post the build I'll be using here if you'd like. Otherwise it will likely be included in the release the first full week of August.

Thanks for logging this!

[Scott Wells]

Delivered in 2.0.3.1. Note that you will need to regenerate your OST after updating for the fix to take effect.