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

fix: correct a typo in config:set error messaging #424

Merged
merged 2 commits into from
Jun 22, 2022

Conversation

onlywade
Copy link
Contributor

@onlywade onlywade commented Jun 17, 2022

Fixes

When a user enters invalid arguments to the config:set command, the error message mistakenly references an incorrect command name, configs:set:

$ twilio config:set
 » No configuration is added to set. Run "twilio configs:set --help" to see how to set a configurations.

$ twilio configs:set --help
 ›   Error: command configs:set not found

$ twilio config:set --help

update Twilio CLI configurations.

USAGE
  $ twilio config:set
...

This change corrects that mistake in the error message (along with the corresponding test).

Checklist

  • I acknowledge that all my contributions will be made under the project's license
  • I have made a material change to the repo (functionality, testing, spelling, grammar)
  • I have read the Contribution Guidelines and my PR follows them
  • I have titled the PR appropriately
  • I have updated my branch with the main branch
  • I have added tests that prove my fix is effective or that my feature works
  • I have added the necessary documentation about the functionality in the appropriate .md file
  • I have added inline documentation to the code I modified

@childish-sambino childish-sambino changed the title Fix: correct a typo in config:set error messaging fix: correct a typo in config:set error messaging Jun 22, 2022
Copy link
Contributor

@childish-sambino childish-sambino left a comment

Choose a reason for hiding this comment

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

LGTM Thanks!

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.

2 participants