[Feature Request] Adding custom edges to search and query mechanisms

[knavesec]

Hi All,

Awesome tool! I've been working on some development of new edges and such for my own use, but when I use any of the built in search/pathfinding mechanisms it will only use the edges in BH, not my custom edge. In the source code, this is because each edge can be toggled, so when building search queries it uses the format edge1|edge2|edge3 instead of just a *1.. for everything. Understandably, this is necessary to be able to omit edges since Cypher doesn't really allow that, but it makes any additional edges more difficult to use.

My two current solutions are editing the source code to fix it, or simply using the custom query bar and including every single attribute in the search, including the desired new edge. This however is not particularly easy or convenient for the masses, nor efficient.

What I would love to see would be a way to add a new edge to the search parameters. In the filter drop down list would make the most sense to me (but maybe there's a better place), perhaps with a + button or something.

Again, great tool, would just love a little more extensibility for custom dev and tool use!