You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
compareToIgnoreCase produces wrong order. For example server response 15 and 5 sortText. After compareToIgnoreCase 5 will be before 15, when should be after
The text was updated successfully, but these errors were encountered:
DocumentFilter have main priority, and this is a reason why I sometimes have strange results in JS files after "dot" or operators
Completions aren't re-sorted after filtering. CompletionProposalPopup#computeFilteredProposals just show/hide proposals, so in current state, if completion was invoked after first letter (for example new d|), and filtered is based on letters only (position isn't re-checked) most of completions have no sense, and it's mostly noise!
compareToIgnoreCase produces wrong order. For example server response 15 and 5 sortText. After compareToIgnoreCase 5 will be before 15, when should be after
The text was updated successfully, but these errors were encountered: