8000 Mentioned the case-insensitivity of command shortcuts by javiereguiluz · Pull Request #8524 · symfony/symfony-docs · GitHub
[go: up one dir, main page]
Skip to content

Mentioned the case-insensitivity of command shortcuts #8524

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.

Sign up for GitHub

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
Oct 29, 2017
Merged

Mentioned the case-insensitivity of command shortcuts #8524

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a51f56b
Mentioned the case-insensitivity of command shortcuts
javiereguiluz Oct 18, 2017
c28a051
Fixed typo
javiereguiluz Oct 18, 2017
6af99da
Fixed a grammar issue
javiereguiluz Oct 28, 2017
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
10 changes: 10 additions & 0 deletions components/console/usage.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -148,6 +148,16 @@ can run it with:

$ php application.php d:g Fabien

# as long as it's unambiguous, you can also mix upper and lower case
# php application.php Demo:g Fabien
# php application.php de:Gr Fabien
# php application.php DE:Gre Fabien

If you enter a short command that's ambiguous (i.e. there are more than one
command that match), then no command will be run and some suggestions of
the possible commands to choose from will be output.

.. versionadded:: 3.4
Case-insensitivity of command shortcuts was introduced in Symfony 3.4. In
previous Symfony versions, shortcuts must match the case of the original
Copy link
Member

Choose a reason for hiding this comment

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

[...] shortcuts had to match [...]

command name (e.g. ``d:g`` was not the same shortcut as ``D:G``).
0