Add functions to EntrySearcher accepting crazy terms for internal code use #3760
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.
Type of change
Description and Context
To properly fix #3729, we need a way to pass arbitrary terms to the entry searcher, bypassing the limitation of the search term minilanguage. I also removed
QSharedPointer
usage in search terms. These are not shared in multiple places and there's no benefit usingQSharedPointer
over using struct value directly.EntrySearcher::SearchTerm
andEntrySearcher::Field
are now publicEntrySearcher::search
andEntrySearcher::searchEntries
accepting search terms directlyQSharedPointer
usageTesting strategy
testfdosecrets.cpp
testfdosecrets
andtestentrysearcher
Checklist:
-DWITH_ASAN=ON
. [REQUIRED]