Thomas Wang
Thomas Wang
Fixed in the pull request.
All true. Lists sorted case insensitively have ill defined ordering and they are incompatible with binary tree optimizations. For example, a SortedMap with case insensitive ordering has bugs. In my...
Pull request 36 might solve your issue. The current default compareTo(a,b) in AbstractCompletion violates natural ordering; so that need to be fixed first.
It appeared that there is an implicit requirement that each implementation of a Completion natural comparison order needs to have the inputText as a prefix. This is in order to...
I have studied this class a bit more. For now the workaround is to change the previous example from: ``` TemplateCompletion tc = new TemplateCompletion(cp, "function()", "new function", template); ```...
In these situations it is easier to sort using an external comparator. It is less buggy if all completions are ordered by source text only (say case insensitive primary ordering,...
In my product I set all AutoCompletion attributes before I call the install() method. Not sure if this is the cause.
I have fixed this issue. Working on pull request today.
Hmm, but the completions array in AbstractCompletionProvider was declared with "protected" visibility. You can't switch out the implementation because some client code may already have a dependency on its data...