[Eli Pinkerton (wallstop)]

DISCLOSURE: LLM-GENERATED TEXT

Why: The popover close buttons and the Settings data folder Select button were the last commands without a hover hint.

What:

• Hint every popover close button
• Name the Settings data folder Select command on hover
• Cover all six popovers and the settings data folder row

Refs #312

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

Popover close buttons now show a tooltip with the current cancel key. The Settings data-folder Select button has a tooltip describing its action. Editor tests check the hints across popovers and with a remapped cancel key.

Changes: Popover tooltip hints

Layer / File(s)	Summary
Add and validate popover tooltips Editor/DataVisualizer/DataVisualizer.cs, Tests/Editor/PopoverFocusTests.cs, CHANGELOG.md	A shared helper adds a dynamic cancel-key tooltip to close buttons across six popover types. The Settings folder Select button has an action tooltip. Editor tests check these hints and verify that the close-button tooltip reflects a remapped key.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related issues

• Clarify catalog controls and consolidate row actions #312 — This change adds popover close-key hints and a Settings folder command hint, which align with the issue’s described usability and control-affordance work.
• Improve SO workflows, scalability, and documentation #305 — The supplied context describes this as the parent usability initiative for #312; this change contributes popover and folder-button hints.

Possibly related PRs

• Ambiguous-Interactive/DxVisualizer#507 — This PR changes focus restoration for popover close actions; this change updates the close buttons used by those actions.

Merge Risk: Minimal · up to 15b40

The hints no longer advertise a misleading cancel key. No merge-blocking issue remains identified.

Pre-merge checks: 4 · 1

Failed checks: 1 warning

Check name	Status	Explanation	Resolution
Docstring Coverage		Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…	Write docstrings for the functions missing them to satisfy the coverage threshold.

Passed checks: 4 passed

Check name	Status	Explanation
Title check		The title clearly and concisely describes the main change: adding hints to popover close buttons and the folder button.
Description check		The description clearly states why the change exists and lists the three main changes. It omits the template's Type of Change and Checklist sections, but the core description is complete.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 7 functions across 2 files. (1 skipped: 1 unsupported.)

Resolution

Write docstrings for the functions missing them to satisfy the coverage threshold.

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Warning

Some tools did not complete. Review the errors below.

ast-grep (0.51.1)

ast-grep could not parse rule config: /ast-grep-rules/ast-grep-essentials/rules/javascript/security/variable-sql-statement-injection.yml

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.

Recent review details

Context from checks skipped due to timeout: 1

• GitHub Check: CodeRabbit

Additional context used

Code guidelines: 1

.llm/context.md — auto-discovered

Path-based instructions: 2

Applicability reference: AGENTS.md: # Repository Guidelines See the [AI Agent Guidelines](./.llm/context.md) for all AI agent guidelines.

CodeRabbit inference engine (.llm/context.md)

Files:

• Tests/Editor/PopoverFocusTests.cs
• Editor/DataVisualizer/DataVisualizer.cs

Applicability reference: AGENTS.md: # Repository Guidelines See the [AI Agent Guidelines](./.llm/context.md) for all AI agent guidelines.

CodeRabbit inference engine (.llm/context.md)

Files:

• CHANGELOG.md

Learnings: 2

Common learnings

Learnt from: CR
Repo: Ambiguous-Interactive/DxVisualizer PR: 0
File: .llm/context.md:0-0
Timestamp: 2026-10-31T05:33:39.058Z
Learning: Applies to **/*.cs : Applicability reference:
AGENTS.md: # Repository Guidelines
See the [AI Agent Guidelines](./.llm/context.md) for all AI agent guidelines.

Source excerpt:
# LLM Agent Instructions

## Critical Rules

### C# and Unity

28. Name every C# method in PascalCase without underscores, including test methods. The C# source lint enforces this convention independently of IDE diagnostics.

Learnt from: CR
Repo: Ambiguous-Interactive/DxVisualizer PR: 0
File: .llm/context.md:0-0
Timestamp: 2026-10-31T05:33:39.058Z
Learning: Applicability reference:
AGENTS.md: # Repository Guidelines
See the [AI Agent Guidelines](./.llm/context.md) for all AI agent guidelines.

Source excerpt:
# LLM Agent Instructions

## Critical Rules

### C# and Unity

2. Format every modified `.cs` file with CSharpier 1.1.2 (print width 180 in `.csharpierrc`; `dotnet tool run csharpier -- format <paths>`) and every modified `.md` file with
   Prettier (print width 180 in `.prettierrc.json`; `npm run format:md`); treat both as gates. Generated and skill Markdown is exempt (`.prettierignore`), and table cells align to
   their widest cell, so table lines may exceed the width.

Learnt from: CR
Repo: Ambiguous-Interactive/DxVisualizer PR: 0
File: .llm/context.md:0-0
Timestamp: 2026-11-02T20:14:27.735Z
Learning: Applies to **/*.cs : Applicability reference:
AGENTS.md: # Repository Guidelines
See the [AI Agent Guidelines](./.llm/context.md) for all AI agent guidelines.

Source excerpt:
# LLM Agent Instructions

## Critical Rules

### C# and Unity

2. Format every modified `.cs` file with CSharpier 1.1.2 (print width 180 in `.csharpierrc`; `dotnet tool run csharpier -- format <paths>`) and every modified `.md` file with
   Prettier (print width 180 in `.prettierrc.json`; `npm run format:md`); treat both as gates. Generated and skill Markdown is exempt (`.prettierignore`), and table cells align to
   their widest cell, so table lines may exceed the width.

Learnt from: CR
Repo: Ambiguous-Interactive/DxVisualizer PR: 0
File: .llm/context.md:0-0
Timestamp: 2026-11-01T05:48:38.269Z
Learning: Applies to **/*.cs : Applicability reference:
AGENTS.md: # Repository Guidelines
See the [AI Agent Guidelines](./.llm/context.md) for all AI agent guidelines.

Source excerpt:
# LLM Agent Instructions

## Critical Rules

### C# and Unity

3. Resolve analyzer warnings before review.

Learning: 2026-10-31T05:33:39.058Z

Learnt from: CR
Repo: Ambiguous-Interactive/DxVisualizer PR: 0
File: .llm/context.md:0-0
Timestamp: 2026-10-31T05:33:39.058Z
Learning: Applies to **/*.cs : Applicability reference:
AGENTS.md: # Repository Guidelines
See the [AI Agent Guidelines](./.llm/context.md) for all AI agent guidelines.

Source excerpt:
# LLM Agent Instructions

## Critical Rules

### C# and Unity

29. Use `//` for standalone single-line comments and tool control directives only. Write ordinary multi-line explanations as one indented `/* ... */` block. Keep `///` XML
    documentation line-oriented. The C# source lint enforces this rule.

Applied to files:

• Editor/DataVisualizer/DataVisualizer.cs

[coderabbitai]

• Fix comments: Fix CodeRabbit comments on this PR