-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Tweak handling of aliases #5468
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
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
r=me, nice! |
@bors r=alexcrichton |
📌 Commit e4e3177 has been approved by |
⌛ Testing commit e4e31776f56307a68962e85020386083e7bfc1e0 with merge d25fb85f77e29053b54d4d12782411f15b019845... |
💔 Test failed - status-travis |
Previously, `execute_subcommand` was called recursively, and each call would `.configure` the `config` again. It worked, but seemed rather fragile. This commit handles aliases more explicitly, ensures that `.configure` is called once and, as a bonus, adds a warning for when an alias is shadowed by the built in.
By convention, all errors should start with a lowercase letter
@bors r=alexcrichton |
📌 Commit ecd1e5d has been approved by |
Tweak handling of aliases Previously, `execute_subcommand` was called recursively, and each call would `.configure` the `config` again. It worked, but seemed rather fragile. This commit handles aliases more explicitly, ensures that `.configure` is called once and, as a bonus, adds a warning for when an alias is shadowed by the built in.
☀️ Test successful - status-appveyor, status-travis |
Previously,
execute_subcommand
was called recursively, and each callwould
.configure
theconfig
again. It worked, but seemed ratherfragile.
This commit handles aliases more explicitly, ensures that
.configure
is called once and, as a bonus, adds a warning for when an alias is
shadowed by the built in.