-
Notifications
You must be signed in to change notification settings - Fork 7
DOC-799 | Graph Visualizer improvements and updated screenshots #802
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Deploy Preview Available Via |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is being reviewed by Cursor Bugbot
Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
<span class="inline-icon" aria-hidden="true"> | ||
{{- $iconName := .Get 0 }} | ||
{{- $iconPath := printf "/images/icons/%s.svg" $iconName }} | ||
{{- $iconSvg := readFile $iconPath }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: Icon Shortcode Path Mismatch
The icon
shortcode constructs icon paths as /images/icons/NAME.svg
for readFile
. However, readFile
interprets paths starting with /
relative to the project root, meaning it looks in PROJECT_ROOT/images/icons/
. This path doesn't match the actual icon file location in site/content/images/icons/
, causing icons to be unfound and triggering an error.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works and is also correct according to the Hugo docs:
The os.ReadFile function attempts to resolve the path relative to the root of your project directory. If a matching file is not found, it will attempt to resolve the path relative to the contentDir. A leading path separator (/) is optional.
https://gohugo.io/functions/os/readfile/
We can change it to "site/content/images/icons/%s.svg"
though.
{{< /tip >}} | ||
|
||
The **Graph Visualizer** is a browser-based tool integrated into the web interface | ||
of the ArangoDB Platform. It lets you explore the connections of your named graphs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
of the Arango Data Platform. It lets you explore the connections of your named graphs |
### Select and load a graph | ||
|
||
1. In the ArangoDB Platform web interface, select the database your named graph | ||
1. In the Data Platform web interface, select the database your named graph |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1. In the Data Platform web interface, select the database your named graph | |
1. In the Arango Data Platform web interface, select the database your named graph |
2. Click the _palette_ icon in the top right to open the **Customization** panel | ||
1. Click the **Legend** button in the top right to open the **Legend** panel | ||
if it's closed. | ||
2. Select the **Nodes (#)** tab and click one of the node collections. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Step 3 is missing in the numbered list
|
||
### View node and edge properties | ||
|
||
You can inspect the document attributes of node or edge as follows: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can inspect the document attributes of a node or edge as follows: |
hierarchies, and relationship flows. You can also download an image of what is | ||
displayed. | ||
|
||
- **Minimap**: A small overview to easier navigate the canvas. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- **Minimap**: A small overview to easier navigate the canvas. | |
- **Minimap**: A small overview for easier canvas navigation. |
- Optionally provide a JSON body to use as the document content. | ||
4. Click **Create** to add the node to the canvas and database. | ||
|
||
### Create New Edges |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
### Create New Edges | |
### Create new edges |
- **Color** | ||
- **Icon** | ||
- **Display**: What attribute to use for the label and what information | ||
to show in the tooltip when hovering a nodes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to show in the tooltip when hovering a nodes. | |
to show in the tooltip when hovering over nodes. |
|
||
### Add nodes and edges using a query based on a selection | ||
|
||
You can select nodes and edges on the canvas and then use a **Canvas Action**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Canvas Actions feature could use a better introduction, right now it jumps directly into technical details. We should start with a clear definition, add some common use cases, and then explain how it works. I'd suggest something like:
Canvas Actions are predefined AQL queries that work with your current selection of nodes and edges on the canvas. Think of them as tools that let you discover related data based on what you've already selected. Unlike regular queries that work on the entire graph, Canvas Actions use special bind variables (
@nodes
and@edges
) to reference your selected items, making them context-aware and interactive.
We should also list some real-world examples that users can relate to... e.g. find all customers who bought the same products as the selected customers
## Visual customization | ||
## Legend | ||
|
||
### Visual customization |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would restructure this into different sections e.g. Customize node appearance, Customize edge appearamce, Save and manage themes, ... along with some real-world examples (why would you use different colors for different node types). For example, in a recommendation system you might want to use different colors for different product categories and edge thickness to show recommendation strength.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see my comments.
3. Select a graph from the list. | ||
4. The viewport of the Graph Visualizer opens for exploring the graph. | ||
|
||
The main area of the viewport may initially be empty in the following cases: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will change, the Visualizer will automatically populate the canvas with an initial neighbourhood, see https://github.com/arangodb/platform-ui/pull/217
Description
Upstream PRs