Query related entities by relation name
exploring
Gur Shafriri
Currently, when searching for related entities, all related entities in the blueprint specified will be returned.
This feature will allow for the specification of the relation path, allowing different visualizations to be based on it.
For example, Create separate tables for 2 types of relations to the same entity.
Gur Shafriri
exploring
Gur Shafriri
Merged in a post:
In the related entities use the name of the relation in the tab
Kostis Kapelonis
Right now in the related entities tab the name of the target entity is used. This works well for simple cases.
But for more advanced cases where the name of the relationship is important or where multiple relations share the same target entity, it would be best to show the name of the relationship instead of the entity in the tab
Gur Shafriri
Merged in a post:
Allow filtering by relation in tables and graph view
M
Mark-Oliver Junge
In cases where we have 2 blueprints that are related through more than 1 type of edge, it would be extremely useful to filter by the type of relation.
Suppose the attached model, with commits being linked to builds through a single relation (head_commit) and a many relation (commit_history). I would like to be able to on the page for a commit, filter the graph for only builds with that commit as the head commit.
(Sidenote: It would also be nice, if there is 2 edges between 2 nodes to display both. In this example it shows 3 relations as commit_history, but they are also related by head_commit, which is hidden)