-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[search in workspace] Unstable ordering of search results #4113
Comments
@svenefftinge I wonder if it would be useful to not trigger re-search whenever the search and options remain the same. Keeping the history of past searches can be useful since I also noticed |
Moved from #4416 (comment): I got back different hit counts for the same query term. See attached screencast. |
Fixes #4113 Currently, the `search-in-workspace` result order is not consistent/stable and can lead to different ordering between search results. The fix was to ensure that the tree is properly rendered in order in the `onDone` callback. The first step is to sort by the `root folders` and then update it's children by sorting them as well. Signed-off-by: Vincent Fugnitto <[email protected]>
Fixes #4113 Currently, the `search-in-workspace` result order is not consistent/stable and can lead to different ordering between search results. The fix was to ensure that the tree is properly rendered in order in the `onDone` callback. The first step is to sort by the `root folders` and then update it's children by sorting them as well. Signed-off-by: Vincent Fugnitto <[email protected]>
Fixes #4113 Currently, the `search-in-workspace` result order is not consistent/stable and can lead to different ordering between search results. The fix was to ensure that the tree is properly rendered in order in the `onDone` callback. The first step is to sort by the `root folders` and then update it's children by sorting them as well. Signed-off-by: Vincent Fugnitto <[email protected]>
Fixes #4113 Currently, the `search-in-workspace` result order is not consistent/stable and can lead to different ordering between search results. The fix was to ensure that the tree is properly rendered in order in the `onDone` callback. The first step is to sort by the `root folders` and then update it's children by sorting them as well. Signed-off-by: Vincent Fugnitto <[email protected]>
The ordering of search results isn't ordered consistently but is different on every search.
Reproduce:
(trigger search several times)
The text was updated successfully, but these errors were encountered: