Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.6k
[Console] Fix issue with reserved keyword "command" as argument name#54795
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:7.4
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Thanks for the PR. Although it is hack-ish, I'm ok with the argument description' string-based check. Changing the milestone for 7.2 also as 7.1 is in feature-freeze and this is a DX improvement, not a bugfix. |
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
An alternative could be to rename the internal |
flkasper commentedMay 4, 2024 • edited by chalasr
Loading Uh oh!
There was an error while loading.Please reload this page.
edited by chalasr
Uh oh!
There was an error while loading.Please reload this page.
See discussion at#54729. It would also be a major breaking change. |
Uh oh!
There was an error while loading.Please reload this page.
In the
InputArgument
constructor, anInvalidArgumentException
is thrown if the reserved keywordcommand
is used as the name and is not the argumentcommand name
.The change to this PR is a new non-breaking feature, but could also be merged into older versions as a bugfix.