Inlay Hints — Bound Step Information¶

Each step in a .feature file shows an inline hint after the step text indicating what it’s bound to:

→ ClassName.MethodName for a step with exactly one matching binding.
→ N matches for an ambiguous step (matched by more than one binding).
→ N bindings for a step whose match comes from a templated / Scenario Outline binding.
An undefined step (no matching binding) shows no hint — that case is already covered by the warning diagnostic.

Hovering a hint shows the full signature (declaring type and parameter types) in a tooltip. Hints refresh automatically as you edit.

Visual Studio

Visual Studio does not show the hover tooltip — this is a Visual Studio limitation. The → ClassName.MethodName / → N matches / → N bindings labels themselves display normally.

VS Code

Rider

Enabling / disabling hints¶

There is no Reqnroll-specific setting or hotkey for this — the language server always provides hints when the IDE asks for them, and showing/hiding is entirely each IDE’s own native inlay-hints mechanism:

IDE	How to toggle
Visual Studio	Tools → Options → Text Editor → Advanced, or the equivalent inline-hints display toggle (Alt-F1) — the same generic setting used for any inlay hint, not Reqnroll-specific.
VS Code	Native `editor.inlayHints.enabled` setting (`on` / `off` / `offUnlessPressed` / `onUnlessPressed`). In an `...UnlessPressed` mode, holding the default modifier key (Ctrl-Alt on Windows/Linux, ⌥ on Mac) temporarily shows/hides hints.
Rider	Rider has no inlay-hints Settings page for `.feature` files, so use the Reqnroll: Show Feature Inlay Hints action from Find Action (Ctrl+Shift+A); it toggles binding-info hints in `.feature` editors. On Rider 2026.2 the platform ignores that switch, so the hints cannot be turned off there.