← Back to issue list

Inconsistent parameter syntax

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1771778
Type
issue
State
open
Author
~popey
Labels
—
Created
Updated
Closed
—

Current evaluation

snapcraft close accepts only a single channel while snapcraft release accepts a comma-separated list; syntax remains inconsistent in current code (manage.py StoreCloseCommand).

Suggested action: keep open

Reason: Verified in the current tree that the inconsistency persists: StoreReleaseCommand.run() calls parsed_args.channels.split(",") in manage.py while StoreCloseCommand.fill_parser() defines a single positional "channel", and StoreClientCLI.close() (client.py:1120) forwards only [channel]. The command is still live, not deprecated, and the report is a valid but minor UX/consistency request; the fix is small and well-scoped, though it lacks maintainer triage (no labels, no comments since posting).

Evaluated by: mr-cal-bot

Impact: 22 Quick Win: 12 Complexity: 18 Confidence: 82 Actionability: 65

Issue body

Snapcraft release uses commas:- snapcraft release foo 1 candidate,beta Snapcraft close does not:- root@snapcrafters:~# snapcraft close warzone2100 beta,candidate Could not close channel: Not a valid channel: beta,candidate root@snapcrafters:~# snapcraft close warzone2100 beta candidate Track Arch Channel Version Revision latest amd64 stable 3.2.3 12 candidate ^ ^ beta ^ ^ edge 3.2.3 14 armhf stable 3.2.3 10 candidate ^ ^ beta ^ ^ edge 3.2.3 13 i386 stable 3.2.3 11 candidate ^ ^ beta ^ ^ edge 3.2.3 15 The beta and candidate channels are now closed. This feels inconsistent.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 22
Quick Win: 12
Complexity: 18
Confidence: 82
Actionability: 65
keep open snapcraft close accepts only a single channel while snapcraft release accepts a comma-separated list; syntax remains inconsistent in current code (manage.py StoreCloseCommand).
stealth/space-bunny-alpha
Impact: 5
Quick Win: 4
Complexity: 0
Confidence: 94
Actionability: 88
close stale snapcraft close rejected comma-separated channels while release accepted them. The legacy-command inconsistency is obsolete because snapcraft_legacy has been removed from the current tree.
qwen/qwen3.8-27b
Impact: 15
Quick Win: 13
Staleness: 95
Complexity: 15
Confidence: 60
Support Request: 10
close stale snapcraft release accepts comma-separated channels but snapcraft close does not, requiring space-separated args. 8+ years old, zero comments, no labels, project since completely rewritten.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 30
Confidence: 90
Support Request: 10
close stale Reports inconsistent CLI syntax between snapcraft release and close commands regarding channel parameter separators. Issue is over 8 years old with no maintainer response or activity.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 25
Confidence: 85
Support Request: 10
close stale Reports CLI inconsistency between snapcraft release and close regarding channel parameter syntax. Unaddressed for over 8 years with no maintainer interaction.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 10
Confidence: 80
Support Request: 5
close stale Reports CLI inconsistency where snapcraft release uses comma-separated channels but snapcraft close expects space-separated channels. Untriaged, inactive for over 8 years.

Update history

Date Change
created

Related work

  • Related To: snapcraft (launchpad)#1980155 (confidence 78%)

    Same snapcraft close command; that issue covers a wrong --channel example in help, fixed by 76cc75885, but not the multi-channel syntax gap.

  • Related To: snapcraft (launchpad)#1735800 (confidence 62%)

    Also about snapcraft close argument handling (complaining early with one argument), touching the same positional channel argument.

Related issues

No related issues found above the similarity threshold.