Clarify progress rendering and Spectre capture guidance#22
Merged
carldebilly merged 5 commits intomainfrom Apr 25, 2026
Merged
Conversation
carldebilly
commented
Apr 25, 2026
Member
Author
|
Addressed the review feedback in
Validation:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR clarifies how Repl progress should be reported, rendered, and routed across console, hosted sessions, Spectre, and MCP.
It adds a centralized
docs/progress.mdpage covering:IProgress<double>IProgress<ReplProgressEvent>IReplInteractionChannelprogress helpersOSC 9;4Spectre.Console.ProgressIt also updates the Spectre capture examples to use session-aware
IReplIoContext.Errorinstead ofConsole.Error.Why
Progress behavior was documented in several places, but the full model was not easy to discover. This makes the intended pipeline explicit and calls out an important TUI caveat: Repl progress still has a text fallback label, so app-owned full-screen surfaces should capture or redirect regular Repl interaction feedback.
Validation
dotnet test --project src\Repl.SpectreTests\Repl.SpectreTests.csproj --no-restore