Feature/finished/iia 1279 score order search matching#312
Merged
dholubek merged 4 commits intoikmdev:mainfrom Mar 11, 2025
Merged
Conversation
dholubek
deleted the
feature/finished/IIA-1279-score-order-search-matching
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
https://ikmdev.atlassian.net/browse/IIA-1279
The score order search result did not match exactly from Next Gen Search and Classic Search
The classic search uses a TreeItem in the populateTempRoot() method. The next gen search loads an FXML for the result entries and used a HashMap to hold them, that map was unordered and changing it to a LinkedHashMap to preserve insertion order allowed the logic to match classic Komet
BEFORE:
AFTER:
