Weird suggestions in autocompletion window
The autocomplete window is usually pretty good at figuring out what I am talking about - but I do think that these are kinda a little off the wall - as it turns out, if you use the mouse and double-click them to select/accept them (talking about the "r" options in the attached picture), they're relationship fields (Opportunity__r, etc). I suspect it's just some funky UI bug since it appears - if I bring up the command details by hitting Ctrl + J (Mac), it shows me the right field, and as mentioned above it inserts an actual field.
Comments (10)
-
repo owner -
repo owner -
assigned issue to
- changed version to 1.7.9.3
-
assigned issue to
-
repo owner Derek, I've been unable to reproduce this with my test projects. Can you characterize the underlying project in which this is occurring in a way that might help me to reproduce it? I've tried to get completions for an instance of an SObject with several custom relationship fields which is what I suspect those
r
fields to be, but so far, no go. -
reporter So, the project is as follows:
- Creating a test class for a custom VF controller. No @ TestSetup, etc (which I doubt would affect it).
- The method I first found this on does its own basic test setup - inserting a test account, contact, pricebook, a few custom objects...it is during this setup that I experienced it.
- I can reproduce it readily in virtually any class, on any object that has relationship fields (custom or standard - doesn't matter).
- It would seem that Pricebook2 doesn't produce the result (I suspect as it doesn't have the right kind of relationship fields for some reason???)
- The way I reproduce it is typing "NameOfSobjectVariable.r" and the "r" options are first on the available list. It is also accessible by just finishing on the "." and scrolling to the "r" section of the available list.
- This happens in at least 2 of my environments (the third is production and I only use it to effect SOQL queries and Anonymous scripts)
-
repo owner Thanks, Derek. I'll take a look for 1.7.9.4 since I was able to wrap up a compelling 1.7.9.3 yesterday. I'll let you know if I need additional help reproducing it.
-
repo owner Derek, are you still getting this issue? I feel like I fixed it a bit back, but I'm bouncing back and forth between so many branches right now (1.x, SFDX, and 2.0) that I can't remember if I fixed in 1.x or another branch.
-
reporter I am. Here is an example.
-
repo owner Gotcha. I may have fixed it on the 2.0 branch since I've put a HUGE amount of work there into fixing reference issues...or I may not have fixed it anywhere! I'll investigate a bit and let you know if I need more info from you. Thanks for following up!
-
reporter Sweet - thanks for the updates! I appreciate it very much!
-
repo owner - changed status to resolved
I'm pretty sure this was addressed long ago. Resolving it.
- Log in to comment
Wow, that is weird. I have a few of these from you I need to hunker down and debug! Thanks for reporting...