- edited description
"Create method" quick fix / intention is mostly unresponsive to keyboard input
Issue #1999
resolved
On IJ Idea Ulimate 2021.2.3 after upgrading to IC2 2.1.9.4, I am suddenly finding that my red lightbulb quick fix (is this what JetBrains calls an “intention”? - I am never sure of the lingo) for creating missing Apex methods is no longer responsive to certain keys. Here is an example:
I am trying to add “newMethodIamTryingToAdd()” in the above screenshot. I am able to change the access modifier, e.g., to “public” using the arrows keys, but the return type and return value placeholders are unresponsive to any keyboard input. All I can do is tab out, or hit return to get out of the interaction, then go back and use regular editing to input the values I want.
Please let me know if any additional information, such as logs, etc., might be helpful here.
Comments (7)
-
reporter
-
repo owner
Alan, this is a JetBrains regression that started in 2021.2. I've filed an issue in their public issue tracker and have already been working with them to help isolate and resolve it. I'm hoping they'll be able to provide a workaround that I can implement so I can fix this ASAP, but obviously a fix for the root cause--if done in a timely fashion--would be fine as well. You might add yourself as a watcher on the linked issue for status updates.
-
reporter
Thanks for filing this with JetBrains. I will follow the linked issue.
-
reporter
In your opinion, does this mean it was a bad idea to move onto 2021.2.3? I thought, based on recent IC2 plugin update event descriptions, that the major issues with 2021.2 had been mostly resolved and so it would be timely to switch back. (I have started to run into compatibility issues with other plugin updates while continuing to run on 2021.1.3, which is the version I was stuck on for a long time in order to avoid the IC2 problems).
In other words, what IJ version would you recommend for use with IC2 at this point?
BTW, it seems a bit discouraging that you reported that issue in September of last year, and it doesn’t look as though it has received any attention. Do you think it is likely to get fixed? I rely heavily on these templates, and am not sure what course of action to take if they are not going to work.
-
repo owner
Alan, the issue was reported just a few weeks ago, and the person to whom it is assigned--someone I work with closely--is currently on vacation. As soon as he's back I'll circle back around with him.
I'm using 2021.2.3, and I'm recommending that to others. This is the only remaining issue with 2021.2 of which I'm aware, and while annoying, it's certainly not blocking. Also, I'm hoping that between Yann and myself we'll find a resolution when he returns. Having said that, definitely feel free to drop back to 2021.1.3 if this is affecting your productivity, and then either via this issue or the YouTrack one, I'll let you know when it's save to move back up.
-
repo owner
- changed status to resolved
Alan, I was just doing some testing in the latest 2021.3 EAP build and found that this issue has already been resolved by JetBrains there. Unfortunately that doesn't help things in 2021.2, but since this is a JetBrains bug and 2021.3 will be out relatively soon with the fix, there's not likely anything for me to do. I can request that they back-port it to 2021.2, but at this point I think moving to 2021.3 once it has been released is likely the better plan. So far I'm finding the 2021.3 EAP builds to be much higher quality than the last two (hopefully not famous last words).
-
reporter
Excellent. I do appreciate the insight into versions, etc., and this isn’t such a terrible defect that I can’t live with it until 2021.3. Once again, thanks for the guidance. (Sometimes it’s hard to know what to do for the best, in the shifting landscape of different versions.)
- Log in to comment
