‎2019 Oct 21 3:44 PM
Shouldn't the "create method" quick fix take the parameters from the coding?!
It seems not to:

My understanding - which might be wrong - is, that I write down the method call (with parameters), quick-fix to create that method i just 'described'/used and then go ahead an fill it with coding.
‎2019 Oct 21 4:00 PM
Might be something wrong with my backend - when trying to create that method, I get a dump OBJECTS_OBJREF_NOT_ASSIGNED in CL_RFAC_METHOD_INSERTER=======CP

‎2019 Oct 21 8:45 PM
‎2019 Oct 22 1:19 PM
You can use either CALL METHOD (please don't) or the functional style with brackets. Here you are using brackets with CALL METHOD. You should get a syntax error.
‎2019 Oct 22 3:25 PM
Once the method is created, it ("using brackets with CALL METHOD") seems fine syntax wise:

But I do get and appreciate what you are getting me towards!
(I'm trying to refactor legacy coding while also trying to get back into AdT, while also trying to utilize it's refactoring features.
I guess that might be to much in combination - I'll probably try the AdT features on a playground report, without the burden of legacy code... )
Btw. Version are:
Eclipse 2019-09
AdT 3.4.4
‎2019 Oct 22 3:51 PM
OK, I can narrow it down to this:
When using "create method" quick fix to create a new method to an interface, the parameters are not taken from the code:

‎2019 Oct 22 3:53 PM
For reference, this is how it works on a method of a class:
(and how I also would suspect it for a method of an interface?!)

‎2019 Oct 23 12:11 AM
You are right, it does not work yet. - But you can first create (by Quick Fix) the method in the class, and then you can refactor that method and "pull" (also by Quick Fix) it to the interface:
