Community
Participate
Working Groups
The order for string externalization quick fixes is different when invoked by clicking on the marker on the left margin compared to one that comes by pressing Ctrl + 1 on the non-NLS'ed string. See snapshots
Created attachment 190116 [details] snapshot
Created attachment 190120 [details] Snapshot
Nope, it's not different. When you click on the ruler then you click on the warning and hence Quick Fix/Assist is invoked on that selection. If you use Ctrl+1 on that selection you'll get the same ordering.
When clicking on the warning and hence quick fix being triggered, shouldn't the 'fix' that fixes the problem should be of top relevance? That is, the non-nls and externalize string quick fix should be shown on top.
There could be more than one warning/error and below could be the quick assist icon/trigger. We simply select the most relevant selection and invoke Ctrl+1, so that you get exactly the same result as when invoking Ctrl+1 on the selection manually.
Dani is right that the order is consistent if the selection is the same, but I also agree with comment 4. I've increased the relevance of the nls proposals to beat the Extract... ones even if there is a selection. Fixed in HEAD of LocalCorrectionsSubProcessor.
The fix looks good, thanks Markus! Ankur, thanks for the bug report :)
Verified the order is correct for 3.6 M6 with N20110305-2000.