Follow-up to #18 / #39. As of #39, hovering an ambiguous step lists every colliding step-definition binding (step type, expression, method) as plain text — matching the legacy VS extension's behavior. Navigation to one of those bindings is still a separate gesture: F12 / "Go to Step Definition" already returns all matches and (in VS Code) shows a quick-pick to choose which one to jump to. The two aren't wired together.
Open question: should hovering an ambiguous step let you navigate directly to a selected binding from the popup itself, rather than requiring a second F12 gesture?
Possible approaches, roughly in order of how well-supported they are across VS/VS Code:
- Leave as-is. Hover shows the list, F12 does the picker-navigation. Two gestures, but both already exist and work.
- Code Action at the diagnostic range — e.g. "Go to
CalculatorSteps.AddNumbers" per colliding binding, offered as a quick fix / lightbulb at the ambiguous step. Well-supported, clickable in both editors, and can reuse the same binding list GoToStepDefinitionsHandler already computes.
- LSP
DiagnosticRelatedInformation (locations attached to the diagnostic) — standard LSP mechanism, but editor support for making these clickable from the hover popup itself (as opposed to the Problems/Error List panel) is inconsistent.
Posting this as an open question to get community feedback before committing to an approach — no urgency, current behavior (hover + F12) is functional.
Follow-up to #18 / #39. As of #39, hovering an ambiguous step lists every colliding step-definition binding (step type, expression, method) as plain text — matching the legacy VS extension's behavior. Navigation to one of those bindings is still a separate gesture: F12 / "Go to Step Definition" already returns all matches and (in VS Code) shows a quick-pick to choose which one to jump to. The two aren't wired together.
Open question: should hovering an ambiguous step let you navigate directly to a selected binding from the popup itself, rather than requiring a second F12 gesture?
Possible approaches, roughly in order of how well-supported they are across VS/VS Code:
CalculatorSteps.AddNumbers" per colliding binding, offered as a quick fix / lightbulb at the ambiguous step. Well-supported, clickable in both editors, and can reuse the same binding listGoToStepDefinitionsHandleralready computes.DiagnosticRelatedInformation(locations attached to the diagnostic) — standard LSP mechanism, but editor support for making these clickable from the hover popup itself (as opposed to the Problems/Error List panel) is inconsistent.Posting this as an open question to get community feedback before committing to an approach — no urgency, current behavior (hover + F12) is functional.