Filter entities in the UI (part 8): Make the query semantics more powerful #8886
+1,230
−133
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.
Related
CustomContent
more useful #8645re_blueprint_tree
and add more tests #8795re_time_panel
and add more tests #8863What
This PR improves on the filter semantics.
Filters now accept multiple, whitespace separated keyword. For an entity to match, every keyword must be found in full in one of the entity's parts. For the blueprint tree, only the actually visible parts are considered.
Since having a
/
in a keyword doesn't wort as expected, it's for now disallowed entirely in the text edit.This PR extend the existing
re_blueprint_tree
tests and introduce a whole new test suite inre_time_panel
(both insta and kittest).