Skip to content

Introduce IFalloutCommand dispatch with DI for Fallout.Cli (#392, PR 0)#16

Open
ChrisonSimtian wants to merge 4 commits into
mainfrom
cli-command-dispatch-foundation
Open

Introduce IFalloutCommand dispatch with DI for Fallout.Cli (#392, PR 0)#16
ChrisonSimtian wants to merge 4 commits into
mainfrom
cli-command-dispatch-foundation

Conversation

@ChrisonSimtian

Copy link
Copy Markdown
Owner

Replaces the reflection-over-Program CLI dispatch with one-command-per-type behind a typed IFalloutCommand, resolved via Microsoft.Extensions.DependencyInjection. PR 0 of an incremental series — lands the abstraction, dispatcher, and first conversion; a transitional adapter keeps the other 13 handlers working so nothing regresses.

What changed

  • IFalloutCommand + CommandDispatcher replace Program.Handle; resolution stays dash/case-insensitive (every spelling the old reflection accepted).
  • IConsolePrompts / SpectreConsolePrompts — Spectre prompt helpers lifted off Program into an injectable service.
  • RunCommand — first real conversion. DelegateCommand adapts the 13 still-legacy handlers so dispatch is uniform; each follow-up PR deletes one.
  • Reflection dispatch removed; CommandDispatcherTests add first dispatch coverage.

Why it's not breaking

Fallout.Cli is the tool Exe, not a consumed library; the :command surface and shell-function names are preserved exactly. Hence target/2026 / main, no breaking-change label.

Verification

dotnet build src/Fallout.Cli clean · Fallout.Cli.Tests 30 pass · fallout :bogus prints the full command manifest.

Follow-ups (Fallout-build#392): setup · update · add-package · cake-convert/clean · complete · get-configuration · secrets · trigger · navigation → then collapse Program to a thin entry point.

Part of Fallout-build#392.


Re-raised fork-internally to move the cli-cmd stack off the main repo. Supersedes Fallout-build#394; same history and diff.

🤖 Generated with Claude Code

ChrisonSimtian and others added 4 commits July 2, 2026 09:18
Replace the reflection-over-Program command dispatch (the partial god-class
described in Fallout-build#392) with a typed command abstraction resolved through
Microsoft.Extensions.DependencyInjection. This is the foundation PR: it lands
the abstraction, the dispatcher, the prompt service, and the first real command
conversion, with the remaining handlers converted one per follow-up PR.

- Add public IFalloutCommand (Name + Execute) and a CommandDispatcher that
  resolves by name, dash- and case-insensitively, preserving every spelling the
  old reflection accepted (:add-package == :addpackage, :PopDirectory, ...).
- Move the Spectre prompt/render helpers off Program into an injectable
  IConsolePrompts / SpectreConsolePrompts (namespace Fallout.Cli.Prompts to
  avoid colliding with System.Console). Program keeps thin static delegators so
  the not-yet-extracted handlers compile; the last conversion deletes them.
- Convert Run into a real RunCommand type; delete Program.Run.cs.
- Adapt the 13 still-legacy handlers via a transitional DelegateCommand so the
  registry and dispatch are uniform from day one. Each future PR deletes one
  registration line plus its Program.X.cs partial.
- Delete the reflection dispatch and its "add assertions about return type and
  parameters" TODO; typed commands make signature-mismatch dispatch impossible.
- Add CommandDispatcherTests (first-ever dispatch coverage): name matching,
  dash/case insensitivity, exit-code passthrough, unknown-command listing,
  empty token, and all default-routing branches.
- Add .vscode launch/build tasks for debugging the global tool from source.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Bump the cross-command helpers (GetConfiguration(buildScript, evaluate),
AddOrReplacePackage, WriteBuildScripts, WriteConfigurationFile, GetTemplate,
PrintInfo, CurrentBuildScriptName, BUILD_PROJECT_FILE) from private to internal
so the per-command IFalloutCommand types extracted in the Fallout-build#392 follow-up PRs can
call them during the transition. These move into dedicated services in the final
collapse PR; this is the minimal enabler that lets each command be converted in
an independent, conflict-free PR.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
we currently dont plan to expose any of those, so we can make these internal. If we need to expose those inside of fallout, we can do so with `<InternalsVisibleTo/>` or at some point make a conscious decision to publish those interfaces for wider, public use

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Address review feedback on Fallout-build#448:
- IFalloutCommand.Execute -> Task<int> ExecuteAsync; RunCommand awaits
  Process.WaitForExitAsync; DelegateCommand adapts the still-sync legacy
  handlers via Task.FromResult; CommandDispatcher.DispatchAsync and Main
  become async. No behavior change and no public-API break (Fallout.Cli
  is the tool Exe, not a consumed library).
- Drop the `_` field prefix on the new types (bare field names, this.
  only for ctor assignment collisions).
- Always brace if/for bodies in the new code.

Test method names keep the MethodUnderTest_Scenario_Result style of the
sibling *Specs files; a repo-wide test-naming convention is left to a
dedicated cleanup.

Fallout.Cli.Specs: 30 pass.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@ChrisonSimtian
ChrisonSimtian force-pushed the cli-command-dispatch-foundation branch from 99d3428 to a1e9c8f Compare July 1, 2026 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

target/2026 Releases on the 2026 calendar line

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant