Skip to content

Reworded the explanation about optional command options #5009

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

Merged
merged 3 commits into from
Mar 14, 2015
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions components/console/introduction.rst
Original file line number Diff line number Diff line change
Expand Up @@ -296,9 +296,11 @@ declare a one-letter shortcut that you can call with a single dash like

.. tip::

It is also possible to make an option *optionally* accept a value (so that
``--yell``, ``--yell=loud`` or ``--yell loud`` work). Options can also be configured to
accept an array of values.
There is nothing forbidding you to create a command with an option that
Copy link
Contributor

Choose a reason for hiding this comment

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

that optionally again 👴, it is okay, i will not fuss again about that. Go ahead 👍

optionally accepts a value. However, there is no way you can distinguish
when the option was used without a value (``command --yell``) or when it
wasn't used at all (``command``). In both cases, the value retrieved for
the option will be ``null``.

For example, add a new option to the command that can be used to specify
how many times in a row the message should be printed::
Expand Down