Repository navigation
docs(proposal): interactive TUI mode design for discussion (#710) - #972
Open
delaysystem wants to merge 1 commit into
Open
delaysystem wants to merge 1 commit into
delaysystem wants to merge 1 commit into
Conversation
Design document for the interactive frontend proposed in bee-san#710, following the owner's direction (TUI as a frontend calling the library). Recommends an explicit --interactive flag with a Cargo feature gate, rejects auto-launch and a separate binary for now, and lists open questions for maintainers. No implementation until the discussion outcome exists.
|
This branch has not been deployed
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.
Design-doc PR for #710. Discussion first, no implementation here.
Proposes an explicit
--interactiveflag behind a Cargo feature gate (no auto-launch, no separate binary for now), an additive progress API, and a 6-PR staged series. Open questions Q1-Q6 are in the doc (feature default, flag spelling, progress-API shape, accessibility, auto-launch follow-up, TUI stack).A companion RFC comment is posted on #710 linking back here. Implementation PRs follow once the design is agreed.