Provide fuzzier type member matching and more polished sorting. #629
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #620
Previously, the following completion returned empty results
Now, the completion results include
getTimeStamp
.Since we started allowing fuzzier results, we needed better sorting of
completion items in the same category. For example, in the following
example
we want the results sorted in the following order
This improvement in sorting benefitted non-fuzzy non-type members too.
Previously, the query
Iterator
returned the orderBufferedIterator,Iterator
because they were sorted alphabetically.Now, the order is
Iterator,BufferedIterator
instead, a bigquality-of-life improvement.