1) Soon, the Find Tool will support use of all tools on any one of its results. However, for things like the Highlight Types tool, the compatibility will not be as smooth a process, as it is intended for visual usage. One of the most important features that we must ensure we have readily available is the ability to filter the graph. The Find Tool makes a perfect candidate for being able to filter precise results, a feature we are currently lacking (you can only actually filter types out at the moment). What if a user wants to filter out all nodes with an omnicorp_article_count of less than 500? The Find Tool should allow the user to do this with ease. Obviously, our current method of filtration, hiddenTypes, which is stored in a graph object (App.state.schema and App.state.graph), would have to be adapted to be something along the lines of hiddenAttributes, and would be expanded to something with a structure like
2) The Find Tool's JSONPath syntax supports a sort of query building "helper," where it has arrows letting you explore the graph object without the need to know JSONPath. The problem is, there is no back arrow, so a user who does not know JSONPath and does not wish to have to learn a complex concept (with which they likely have no familiarity) may be left lost when they want to go back a step in the query. Also, it would make it easier, more interactive, and coherent to use in general
1) Soon, the Find Tool will support use of all tools on any one of its results. However, for things like the Highlight Types tool, the compatibility will not be as smooth a process, as it is intended for visual usage. One of the most important features that we must ensure we have readily available is the ability to filter the graph. The Find Tool makes a perfect candidate for being able to filter precise results, a feature we are currently lacking (you can only actually filter types out at the moment). What if a user wants to filter out all nodes with an
omnicorp_article_count
of less than 500? The Find Tool should allow the user to do this with ease. Obviously, our current method of filtration,hiddenTypes
, which is stored in agraph
object (App.state.schema
andApp.state.graph
), would have to be adapted to be something along the lines ofhiddenAttributes
, and would be expanded to something with a structure like2) The Find Tool's JSONPath syntax supports a sort of query building "helper," where it has arrows letting you explore the
graph
object without the need to know JSONPath. The problem is, there is no back arrow, so a user who does not know JSONPath and does not wish to have to learn a complex concept (with which they likely have no familiarity) may be left lost when they want to go back a step in the query. Also, it would make it easier, more interactive, and coherent to use in general