Skip to content

CHANGELOG.md

Latest commit

 

History

History
30 lines (22 loc) · 4.71 KB

CHANGELOG.md

File metadata and controls

30 lines (22 loc) · 4.71 KB
Raw

[vNext]

Improvements:

  • Run CodeLens now resolves each scenario's test target on demand instead of walking the whole .feature file on every refresh, fixing it getting stuck on very large feature files (VS, Rider) - see #495
  • Run CodeLens's Details popup now has a "Show in Test Explorer" action alongside Run/Debug, jumping straight to the test's native pass/fail state and run history (VS) - see #504
  • Run CodeLens now shows the scenario's last-run pass/fail glyph, matching VS's own test CodeLens (VS) - see #504
  • Run, hook-match-count, and step-hooks CodeLenses on a Scenario: line now appear in a deterministic order (Run, then hook count, then step-hooks) instead of an unspecified tie (VS) - see #504
  • Go to Step Definition's ambiguous-match picker now shows the target method's source line instead of a method name/step-type label, built from the standard textDocument/definition response instead of a Reqnroll-specific message (VS Code) - see #126
  • Post-build binding rediscovery now relies solely on the server's standard LSP dynamic file-watch registration instead of a redundant client-side watcher, after confirming the canonical path reliably detects real dotnet builds on its own (VS Code) - see #31
  • .cs binding methods that fail Reqnroll's structural validation (non-static where required, async void, a malformed step expression or [Scope(Tag=...)] tag expression, etc.) now get a live diagnostic squiggle on the offending attribute, merging alongside the IDE's own C# diagnostics for the same file; .feature "step not found" diagnostics also now name the specific reason when the step structurally matches an invalid binding instead of a generic message (LSP server) - see #514

Bug fixes:

  • Fixed the Run action failing with a generic error when dotnet isn't on the IDE process's PATH (e.g. macOS GUI-launched apps) - now falls back to DOTNET_ROOT and well-known install locations, and shows a specific message when dotnet still can't be found (Rider) - see #452
  • Fixed the step-usage "N step usages" CodeLens rendering below the binding method's declaration instead of above it, for connector-discovered bindings (LSP server) - see #484
  • Fixed F2 doing nothing (or erroring "Rename not available at this location") on a .cs binding attribute - now runs Reqnroll's Rename Step, falling back to the native C# rename everywhere else in a .cs file so it doesn't hijack renaming an ordinary symbol, including the binding method's own name (VS Code) - see #506
  • Fixed every step and hook showing as falsely ambiguous when the reflection connector's and Roslyn's source-file paths for the same file disagree (e.g. a PDB path baked in from a devcontainer/CI build vs. the live workspace path, or a stale/unreadable PDB location) - stale connector-discovered bindings are now also superseded by a path-independent identity check (LSP server) - see #469, #503, #515
  • Fixed step-usage CodeLens (and other live-diagnostics features) staying empty for a .cs file that was already open when startup reconciliation completed, until the user's first edit - the didOpen skip-check now confirms the registry actually has bindings for that specific file instead of only checking that the project's connector had run at all (LSP server) - see #517
  • Fixed Go to Step Definition, hook navigation and inlay hints silently doing nothing when the project's assembly was built somewhere else - a devcontainer, a CI agent, another machine, or an external binding package - because the source paths recorded in its PDB don't exist locally. Such a path is now mapped onto the local project where possible; where it can't be, the feature reports why instead of handing the IDE a target it can't open. Find Unused Step Definitions marks those entries as not openable rather than appearing to ignore a click (LSP server, VS, VS Code, Rider) - see #540
  • Fixed the binding registry never refreshing after a rebuild in Visual Studio - it only picked up moved/changed step definitions on the next VS restart, leaving Go to Step Definition, hook navigation, inlay hints and CodeLens pointing at stale positions in between. VS never registers the output-assembly file watcher (it doesn't advertise dynamic registration for it), and its build-finished notification was gated on the output path or target framework having changed, which a plain rebuild never does - that notification now always re-triggers discovery, which is a cheap no-op when the assembly genuinely hasn't changed (LSP server, VS) - see #542

Contributors of this release (in alphabetical order):

Development prior to this changelog is not recorded here — see the commit log for that history.