Refactor container subcommand dispatch #12

New issue

Open

opened 2025-11-19 13:16:57 +00:00 by glenux · 0 comments

glenux commented

2025-11-19 13:16:57 +00:00

Owner

title: Refactor Container Subcommand Dispatch in src/container/cli.cr
description: Streamline the subcommand dispatch logic within DocMachine::Container::Cli, moving away from a single case statement that handles all subcommands.
current_situation: DocMachine::Container::Cli.add_options uses a large case statement within its Proc(Nil) block to dispatch pull, run, save, and load subcommands, including manual args.shift handling.
expected_outcome: Each container subcommand is registered more cleanly, potentially using its own OptionParser block or by structuring the container command itself to properly delegate to dedicated command handlers for pull, run, etc.
technical_details:

Rework the opts.on("container", ...) block in src/container/cli.cr.
Explore defining nested opts.on blocks for pull, run, save, load directly under container.
Ensure argument consumption (args.shift) is tightly coupled to the specific subcommand's parsing rather than a generic block.

--- title: Refactor Container Subcommand Dispatch in `src/container/cli.cr` description: Streamline the subcommand dispatch logic within `DocMachine::Container::Cli`, moving away from a single `case` statement that handles all subcommands. current_situation: `DocMachine::Container::Cli.add_options` uses a large `case` statement within its `Proc(Nil)` block to dispatch `pull`, `run`, `save`, and `load` subcommands, including manual `args.shift` handling. expected_outcome: Each container subcommand is registered more cleanly, potentially using its own `OptionParser` block or by structuring the `container` command itself to properly delegate to dedicated command handlers for `pull`, `run`, etc. technical_details: - Rework the `opts.on("container", ...)` block in `src/container/cli.cr`. - Explore defining nested `opts.on` blocks for `pull`, `run`, `save`, `load` directly under `container`. - Ensure argument consumption (`args.shift`) is tightly coupled to the specific subcommand's parsing rather than a generic block. ---