Project

General

Profile

Bug #3993

Update commands should fail when no parameters are provided

Added by Og Maciel about 8 years ago. Updated almost 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Hammer core
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:
In Kanboard:

Description

# hammer organization create --name myuniqueorg1
Organization created
# hammer organization info --name myuniqueorg1
Id:          109
Name:        myuniqueorg1
Created at:  2014/01/10 22:09:36
Updated at:  2014/01/10 22:09:36

# hammer organization update --id 109 --id 4
Organization updated
# echo $?
0
# hammer organization update --id 109 --new-name
Organization updated
# echo $?
0

I'd argue that the last commands should have returned a non-zero return code and a message stating something along the lines of "you passed redundant arguments" and "missing value for attribute $foo"


Related issues

Related to Hammer CLI - Tracker #2823: Tracker for usability issuesClosed

History

#1 Updated by Tomáš Strachota over 6 years ago

  • Subject changed from Usability issues with hammer cli to Update commands should fail when no parameters are provided
  • Category set to Foreman commands (obsolete)

#2 Updated by Tomáš Strachota over 6 years ago

#3 Updated by Tomáš Strachota over 3 years ago

  • Category changed from Foreman commands (obsolete) to Hammer core

#4 Updated by Shira Maximov almost 2 years ago

  • Status changed from New to Rejected

It is a valid behavior

Also available in: Atom PDF