Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[Console] Revert "bug #41952 fix handling positional arguments"#41966
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
Uh oh!
There was an error while loading.Please reload this page.
Conversation
nicolas-grekas commentedJul 4, 2021
Then we need to also revert the change on the interface, and I'm in favor of deprecating positions in hasArgument and in InputDefinition. The current behavior doesn't make sense when integers are passed. Can you give it a try? |
nicolas-grekas commentedJul 4, 2021
Thank you@chalasr. |
chalasr commentedJul 4, 2021
@nicolas-grekas It appears that handling positions in InputDefinition is required for parsing the raw input (for
|
Uh oh!
There was an error while loading.Please reload this page.
Reverts#41952 as it breaks tests on 5.3 due to an implicit string cast:
We added the
stringtypehint to the$nameargument in 5.x, removing it now to allow forstring|intwould be a BC break which I don't think is worth it.