Interesting, you are suggesting that {{query (property key value}}
should provide the same results by my {{tree key}}
but starting from value
.
I think we should think in terms of “indications to traverse the graph” and “filtering the results”.
At the moment queries are only about filtering results. My proposal is about traversing the graph as a separate feature.
I think we should figure out a way to combine the two i.e. indicate:
- starting nodes with a filter;
- how to traverse the graph (for example following one or more properties);
- filters that apply during the traverse;
- what the results are (final nodes or intermediate ones etc) and how to display them (hierachy, sorting, grouping…).
This may sounds more complex but I think we can find an interface that is both intuitive and whose results are predictable.