This is still a problem for us when editing Gosu code...the Java intention is offered and it inputs syntactically incorrect stuff.
I found this old post:
so it looks like there were some thoughts about how to improve the situation, but I can't find any documentation or examples that would suggest it was actually completed.
It seems to me that, broadly, solutions would fall into three categories:
- A way to un-register the old intention, and replace it with one that delegates to the right language
- An extension to the description so that "language" is part of how an intention is registered
- A level of indirection or delegation, so that intentions find and use language-specific "invoke" implementations
Are any of these now possible? And if not, could someone outline what JetBrains would consider acceptable solutions, so I can estimate how much work it might be to contribute this enhancement?