Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #16645: Command parameter should not be called "Command name" #1139

Conversation

amousset
Copy link
Member

@@ -20,7 +20,7 @@
# @description Execute a command
# @action
#
# @parameter command_name Command name
# @parameter command_name Command to run
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

paremeter will still be named "Command name" if you keep command_name

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in fact all parameter names are

replace "_" by " " and uppercase of first character

@amousset
Copy link
Member Author

PR updated with a new commit

@Normation-Quality-Assistant
Copy link
Contributor

OK, squash merging this PR

@Normation-Quality-Assistant Normation-Quality-Assistant force-pushed the bug_16645/command_parameter_should_not_be_called_command_name branch from b7ff865 to 3725c1b Compare January 29, 2020 23:58
@Normation-Quality-Assistant Normation-Quality-Assistant merged commit 3725c1b into Normation:branches/rudder/6.0 Jan 29, 2020
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants