Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@jeff-matthews
Copy link
Contributor

@jeff-matthews jeff-matthews commented Oct 14, 2025

Purpose

This pull request (PR) updates the Search with Cypher page to reflect the latest features that were released in v8.2.0.

I reviewed a few user stories in the BED-5789 epic to aid in this effort.

  • Restructure the page to focus on prebuilt queries and progressively move into more complexity (i.e., writing custom queries with Cypher syntax)
  • Add new docs and screenshots for key search features (e.g., search/filter, save/save as, import/export)
  • Replace outdated screenshot and terminology
  • Normalize heading syntax
  • Normalize Cypher syntax highlighting and line breaks in code blocks
  • Remove unsupported heading anchor overrides

Questions for reviewers

  • Should we separate this into two pages, where the existing page focuses on UI features and the second page focuses on writing custom queries with Cypher syntax?
  • Is there an existing or preferred convention for callouts on screenshots? I'm not sure about the green line markup that I chose for screenshots in this PR, but I do think it's important to be able to draw attention to specific places in a screenshot.
  • Does the tabbed approach for the Save/Save As workflow steps make sense?
  • Is there any permission related info that I missed re: write access to prebuilt saved queries?

Summary by CodeRabbit

  • Documentation
    • Major overhaul: converted the Cypher search guide into a multi-section, tutorial-style reference with a clearer intro and Quickstart.
    • Expanded step-by-step guidance for searching/filtering, creating/managing saved queries, import/export, and save/edit/share/delete workflows.
    • Added sections for writing custom queries, advanced Cypher concepts, foundational graph elements, standardized terminology, refreshed visuals, and richer examples.

@jeff-matthews jeff-matthews self-assigned this Oct 14, 2025
@jeff-matthews jeff-matthews added the documentation Improvements or additions to documentation label Oct 14, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 14, 2025

Walkthrough

Rewrites docs/analyze-data/cypher-search.mdx from a short reference into a multi-section tutorial-style page. Adds Purpose, What is Cypher?, Quickstart, Features, Create & Manage Queries, Import & Export, Write Custom Queries, Elements of the graph DB, Basic Cypher, Advanced Concepts, updated visuals, and converted code blocks to cql. (36 words)

Changes

Cohort / File(s) Summary of Changes
Docs overhaul: Cypher search tutorial
docs/analyze-data/cypher-search.mdx
Replaced a single CardGroup entry with a structured, multi-section tutorial. Expanded and reorganized content into Purpose, What is Cypher?, Quickstart, Features, Create & Manage Queries, Import & Export, Write Custom Queries, Elements of the graph DB, Basic Cypher, Advanced Concepts, and Outcome. Updated images/assets and changed relevant code blocks to cql.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers

  • StephenHinck

Poem

Thump-thump I bound through docs anew,
I chase the queries, tidy each view.
From Quickstart hops to advanced burrow deep,
I tuck saved searches safe for you to keep.
Carrots of knowledge, exported with glee—🥕

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title "Saved queries (v8.2.0 updates)" is clearly related to the changeset and captures a real, significant aspect of the changes made to the documentation. The PR objectives confirm that the update to the "Search with Cypher" documentation is indeed driven by v8.2.0 features, and saved queries functionality is a major component of the updates, including new sections on creating, managing, importing, and exporting queries. While the title doesn't comprehensively capture the full scope of the restructuring—which also includes expanding sections on basic/advanced Cypher, search/filtering, and normalizing syntax throughout—it is specific, concise, and provides meaningful information about the primary purpose of this documentation update.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch jmatthews/saved-queries-refresh

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b8f333f and 8667a56.

⛔ Files ignored due to path filters (6)
  • docs/assets/edit-saved-query.png is excluded by !**/*.png
  • docs/assets/image1-26.png is excluded by !**/*.png
  • docs/assets/save-query-dialog.png is excluded by !**/*.png
  • docs/assets/saved-queries-default-view.png is excluded by !**/*.png
  • docs/assets/saved-queries-import-export.png is excluded by !**/*.png
  • docs/assets/saved-queries-search-filter.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • docs/analyze-data/cypher-search.mdx (4 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/analyze-data/cypher-search.mdx

[style] ~10-~10: Consider using a more concise synonym.
Context: ...nality of BloodHound. BloodHound offers a variety of prebuilt queries to help you get starte...

(A_VARIETY_OF)


[grammar] ~14-~14: Use a hyphen to join words.
Context: ...ational databases). It uses an ASCII-art style syntax to describe nodes and relat...

(QB_NEW_EN_HYPHEN)


[style] ~205-~205: Consider using “who” when you are referring to people instead of objects.
Context: ...nks. In simple terms, give me any users that are a member of a group up to three lin...

(THAT_WHO)


[style] ~261-~261: ‘joined together’ might be wordy. Consider a shorter alternative.
Context: ...ions on. The two queries we execute are joined together using the WITH keyword. When using ...

(EN_WORDINESS_PREMIUM_JOINED_TOGETHER)

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

♻️ Duplicate comments (2)
docs/analyze-data/cypher-search.mdx (2)

129-131: Typo resolved.

“availble” → “available” fix looks good.


161-162: Alt text added — accessibility fix confirmed.

Alt is present; consider a slightly more descriptive alt if the image shows results (optional).

🧹 Nitpick comments (6)
docs/analyze-data/cypher-search.mdx (6)

14-15: Hyphenation tweak for readability.

-Cypher is a query language for graph databases (similar to SQL for relational databases). It uses an ASCII-art style syntax to describe nodes and relationships. If you can describe the path you're looking for, you can write it in Cypher.
+Cypher is a query language for graph databases (similar to SQL for relational databases). It uses an ASCII‑art‑style syntax to describe nodes and relationships. If you can describe the path you're looking for, you can write it in Cypher.

96-103: “Save As” step likely inverted; rephrase for accuracy.

If the UI has a Save button with a “Save As” option in its dropdown, the action should reference “Save As,” not “Save.”

-          Select a prebuilt or saved query from the list. Click the drop-down arrow beside **Save As** and click **Save** to create a copy of the selected query.
+          Select a prebuilt or saved query from the list. Click the drop-down arrow beside **Save** and select **Save As** to create a copy of the selected query.

Please confirm the exact control labels in v8.2.0 and adjust accordingly.


114-121: Clarify permissions for “Set to Public.”

State explicitly who can edit/delete when public: Owner only? Admins only? Do Editors with share permission gain write? Also clarify whether the owner retains edit rights when set to Public.

Example addition after Line 118:

  • When sharing is set to Public, only Admins (and the query owner?) can edit or delete. View access is granted to all users. Shared users do not gain edit rights unless they are Admins.

166-173: Comma splice/noun list polish.

-Everything in the graph database is represented using common terms from graph theory, particularly **edges,** and **nodes**.
+Everything in the graph database is represented using common terms from graph theory, particularly **edges** and **nodes**.

199-206: Grammar and formatting of repetition range.

  • Use “who” for people and pluralize “member.”
  • Format the repetition as inline code.
-Adding ***1..3** limits the search to relationships that are between one and three links. In simple terms, give me any users that are a member of a group up to three links away.
+Adding `*1..3` limits the search to relationships that are between one and three links. In simple terms, “return any users who are members of a group up to three links away.”

261-261: Tighten phrasing.

-The two queries we execute are joined together using the **WITH** keyword.
+The two queries we execute are joined using the **WITH** keyword.
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8667a56 and 213c95f.

📒 Files selected for processing (1)
  • docs/analyze-data/cypher-search.mdx (4 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/analyze-data/cypher-search.mdx

[style] ~10-~10: Consider using a more concise synonym.
Context: ...nality of BloodHound. BloodHound offers a variety of prebuilt queries to help you get starte...

(A_VARIETY_OF)


[grammar] ~14-~14: Use a hyphen to join words.
Context: ...ational databases). It uses an ASCII-art style syntax to describe nodes and relat...

(QB_NEW_EN_HYPHEN)


[style] ~205-~205: Consider using “who” when you are referring to people instead of objects.
Context: ...nks. In simple terms, give me any users that are a member of a group up to three lin...

(THAT_WHO)


[style] ~261-~261: ‘joined together’ might be wordy. Consider a shorter alternative.
Context: ...ions on. The two queries we execute are joined together using the WITH keyword. When using ...

(EN_WORDINESS_PREMIUM_JOINED_TOGETHER)

🔇 Additional comments (3)
docs/analyze-data/cypher-search.mdx (3)

8-18: Solid restructure and scoping.

Prebuilt-first flow and clear Quickstart are strong improvements. No blocking issues here.

Consider leaving this as one page; if length becomes unwieldy later, split “Create and Manage” vs “Write Custom” into separate pages and add cross-links. Do you want me to draft a split outline?


26-41: Navigation path sanity check.

Confirm “Explore > Cypher > Saved Queries” matches v8.2.0 UI labels and nesting. If labels differ (e.g., “Analyze” vs “Explore”), update for accuracy.


59-69: No change needed: data collectors link is correct
The data collectors link already points to the OpenGraph Library page, which is the central documentation for all collectors.

Likely an incorrect or invalid review comment.

Copy link
Contributor

@StephenHinck StephenHinck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left a couple minor change requests.

We can split it in a separate PR if you like, but this change definitely makes me want to split the "Write Custom Queries" section into its own page. Happy to split that into a separate effort if that makes most sense to you!

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
docs/analyze-data/cypher-search.mdx (1)

204-206: Tighten the grammar in this sentence.

“Give me any users that are a member…” mixes singular and plural. Consider “Give me any users who are members…” for clarity.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0ddd640 and 005fc86.

⛔ Files ignored due to path filters (1)
  • docs/assets/save-query-dialog.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • docs/analyze-data/cypher-search.mdx (4 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/analyze-data/cypher-search.mdx

[style] ~10-~10: Consider using a more concise synonym.
Context: ...nality of BloodHound. BloodHound offers a variety of prebuilt queries to help you get starte...

(A_VARIETY_OF)


[grammar] ~14-~14: Use a hyphen to join words.
Context: ...ational databases). It uses an ASCII-art style syntax to describe nodes and relat...

(QB_NEW_EN_HYPHEN)


[style] ~205-~205: Consider using “who” when you are referring to people instead of objects.
Context: ...nks. In simple terms, give me any users that are a member of a group up to three lin...

(THAT_WHO)


[style] ~261-~261: ‘joined together’ might be wordy. Consider a shorter alternative.
Context: ...ions on. The two queries we execute are joined together using the WITH keyword. When using ...

(EN_WORDINESS_PREMIUM_JOINED_TOGETHER)

🔇 Additional comments (1)
docs/analyze-data/cypher-search.mdx (1)

100-102: Clarify the Save vs. Save As workflow.

This step tells readers to open the Save As menu and then choose Save, which sounds contradictory. Can you double-check the UI flow? If copying requires selecting Save As (or another specific option), please adjust the instructions so users don’t get stuck.

@jeff-matthews
Copy link
Contributor Author

Thanks @StephenHinck! I'll split the page in a separate PR.

Copy link
Contributor

@StephenHinck StephenHinck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SHIP IT!

@jeff-matthews jeff-matthews merged commit c50527f into main Oct 16, 2025
3 checks passed
@jeff-matthews jeff-matthews deleted the jmatthews/saved-queries-refresh branch October 16, 2025 17:04
@github-actions github-actions bot locked and limited conversation to collaborators Oct 16, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants