I recently used the F12 "Go to definition" option to look at the definition of a method which had been overloaded with different signatures in a class and noticed that the navigation incorrectly took me to the first declaration of a method with the matching name despite the method call I'd originated the F12 command from being a call to a different overload of the method with a different list of method parameters. The command should inspect the parameters as well as the method name in order to navigate to the correct method implementation.
"Go to definition" not being able to distinguish between methods of similar name with different arguments in signature
started by
donald.macleod
22 Sep 2017 - 02:40 PM
3 replies to this topic
#2
vlgubanovich
-
-
TWS Team
- 426 posts
Posted 22 Sep 2017
Hi Donnie,
Thank you for reporting this.
We are aware about this - distinguishing between overloaded methods for the "Go to definition" is not yet implemented. We've postponed this functionality to implement it, so we could complete the Lightning, Javascript and Visualforce completion. As we're almost done with this - we'll get back to Apex (and SOQL ;) ) very soon.
Thank you,
Vladimir
Vladimir Gubanovich
Head of Product
The Welkin Suite
skype id: vladimir.gubanovich
e-mail: vladimir.gubanovich@welkinsuite.com
#3
swagattalsania
-
-
Member
- 30 posts
Posted 14 Apr 2018
Hello Vladimir,
Is there any update on this bug? It's been almost 6-7 months now. This is one annoying bug.
Thanks.
Swagat
#4
swagattalsania
-
-
Member
- 30 posts
Posted 10 May 2018
Hi team,
Any updates on this bug? This is becoming annoying now. How can something as important as this not be implemented in the product?