Explain the problem as you see it
I have various search nodes that collect different tags or different facets individually. I need a list of nodes that are combined from different of these search nodes (an aggregation). I tried to create a list of search nodes to get this aggregation, but that doesn't work (see your response above). The only solution I came up with, is to create a new search node that OR combines the various individual searches.
Why is this a problem for you?
This works, but it's a one time operation that is error prone and time consuming. Changes to the original search node need to be manually carried over into the new one
Suggest a solution
Allow for composability of queries (I assume the Query itself is also just a node). So let me compose a new Live query by referencing existing live queries as sub queries
Create a new list type that knows that it consists of search nodes and will "look deeper" into the view
2 Comments
And i found out that this actually already works:
Create a new search node, and in its query, write:
and paste the node references to all the search nodes you want included
a
What would be more awesome would be that you didn’t have to paste the node references into the CHILD_OF value, but could just put a Search node there. As you say, make searches composable.