Issue & PR triage
Loading...
Showing 9 of 9 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
craft-cli issue #347 |
Handle interactive terminal inside emitter stream context | cmatsuoka | 527d | needs triage | 48 | 66 | 12 | Open, untriaged feature request for interactive terminal I/O while Emitter.open_stream captures subprocess output, affecting craft test spread shell and debug flows. |
|
craft-cli issue #261 |
Disable long option abbreviation (`--destructive` vs `--destructive-mode`) | mattculler | 839d | needs triage | 42 | 90 | 29 | Long-option abbreviation remains enabled in _CustomArgumentParser, allowing prefixes such as --destructive to match longer options; the issue is open and awaiting triage. |
|
craft-cli issue #232 |
Capture warnings and present them to developers. | lengau | 995d | needs triage | 42 | 74 | 22 | Maintainer request to route Python warnings through logging.captureWarnings, hide them from normal output, and expose them to developers; still open and untriaged with no implementation found. |
|
craft-cli issue #132 |
The help produced for a command options should give more information | facundobatista | 1387d | needs triage | 42 | 49 | 8 | Enhance option help to show value requirements, defaults, cardinality or repeatability, and choices. The current help pipeline renders option names and messages only, with no recorded design decision. |
|
craft-cli issue #45 |
Simplify the application run/stop cycle | facundobatista | 1794d | needs triage | 40 | 75 | 18 | Maintainer-filed feature request: add an `app_wrapper` context manager to craft-cli to handle emitter init, Dispatcher setup and exception/return-code handling. Design sketched in a 2022 comment; still not implemented in 3.4.x. |
|
craft-cli issue #342 |
Fix all warnings in RTD builds | bepri | 541d | needs triage | 30 | 86 | 21 | RTD has ambiguous cross-reference warnings for CommandGroup and BaseCommand; warning-failure enforcement remains disabled pending closure. |
|
craft-cli issue #78 |
ArgumentParsingError for command not found should hint at the command that raised it | sergiusens | 1651d | needs triage | 28 | 52 | 12 | Feature request: ArgumentParsingError carries no attribute naming the offending command, forcing downstream apps to dig into err.__context__ to distinguish unknown-command errors. Still unimplemented at HEAD. |
|
craft-cli issue #135 |
logging handler is not using any formater | rgildein | 1371d | needs triage | 28 | 60 | 13 | Enhancement request: craft_cli _Handler.emit uses record.getMessage() and ignores self.formatter, so log format can't be customised. Confirmed still unfixed at current HEAD; no maintainer response or labels. |
|
craft-cli issue #243 |
Brief Emitter mode still appears to be verbose when plugins are called ? | flotter | 970d | needs triage | 28 | 30 | 4 | User asks whether BRIEF mode can suppress subprocess output passed through emit.open_stream(); maintainers confirmed subprocess output is intentionally echoed ephemerally in BRIEF and deferred the question of desired behaviour. |