Title: Parameter parsing/passing: an unquoted argument that looks like a named parameter/value pair separated with ":" (colon) is broken in two in positional binding · Issue #6292 · PowerShell/PowerShell · GitHub
Open Graph Title: Parameter parsing/passing: an unquoted argument that looks like a named parameter/value pair separated with ":" (colon) is broken in two in positional binding · Issue #6292 · PowerShell/PowerShell
X Title: Parameter parsing/passing: an unquoted argument that looks like a named parameter/value pair separated with ":" (colon) is broken in two in positional binding · Issue #6292 · PowerShell/PowerShell
Description: Related: #6291 and #6360 Note: Unlike the linked issues, the broken behavior described here only affects PowerShell commands, not also native executables. Steps to reproduce # Basic function without declared parameters that echoes its ar...
Open Graph Description: Related: #6291 and #6360 Note: Unlike the linked issues, the broken behavior described here only affects PowerShell commands, not also native executables. Steps to reproduce # Basic function withou...
X Description: Related: #6291 and #6360 Note: Unlike the linked issues, the broken behavior described here only affects PowerShell commands, not also native executables. Steps to reproduce # Basic function withou...
Opengraph URL: https://github.com/PowerShell/PowerShell/issues/6292
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Parameter parsing/passing: an unquoted argument that looks like a named parameter/value pair separated with \":\" (colon) is broken in two in positional binding","articleBody":"\u003csup>Related: #6291 and #6360\u003c/sup>\r\n\r\nNote: Unlike the linked issues, the broken behavior described here only affects PowerShell commands, not also native executables.\r\n\r\nSteps to reproduce\r\n------------------\r\n\r\n```powershell\r\n# Basic function without declared parameters that echoes its arguments via $Args\r\nfunction Out-Args { $i = 0; $Args | % { 'arg[{0}]: {1}' -f $i++, $_ } }\r\n\r\n# Advanced function that binds all arguments via `ValueFromRemainingArguments` and echoes them.\r\nfunction Out-RemainingArgs { param([parameter(ValueFromRemainingArguments)] $otherArgs) $i = 0; $otherArgs | % { 'arg[{0}]: {1}' -f $i++, $_ } }\r\n\r\n\r\n# Pass a -\u003cparam-nam>:\u003cvalue> argument that looks like a named parameter, but isn't -\r\n# it is bound anonymously, via $Arg / via `ValueFromRemainingArguments`\r\nOut-Args -foo:bar\r\n'---'\r\nOut-RemainingArgs -foo:bar\r\n```\r\n\r\nExpected behavior\r\n-----------------\r\n\r\n```none\r\narg[0]: -foo:bar\r\n---\r\narg[0]: -foo:bar\r\n```\r\n\r\nActual behavior\r\n---------------\r\n\r\n```none\r\narg[0]: -foo:\r\narg[1]: bar\r\n---\r\narg[0]: -foo:\r\narg[1]: bar\r\n```\r\n\r\nThat is, **the single $Args / `ValueFromRemainingArguments`-bound argument was unexpectedly broken _in two_**.\r\n\r\nNote that, by contrast, **the following cases DO work correctly**:\r\n\r\n* **When passing tokens such as `-foo:bar` to _external programs_** - because special effort is already being expended to make this case work (which is needed, because _initially_ all such tokens are parsed as if they were named parameters, even if they later turn out not to be - see [@BrucePay's comment below](https://github.com/PowerShell/PowerShell/issues/6292#issuecomment-372471005).)\r\n\r\n * However, when passing such arguments _indirectly_ to external programs, via `$Args` or `@Args`, the breaking-in-two problem surfaces too - see #6360\r\n\r\n* Had there been a _named_ parameter `$foo` to bind to, things would have worked as expected (the token would have been recognized as a parameter-name/value pair: the `-foo` part would have been used to identify the target parameter, and the `bar` part would have become the parameter variable's value).\r\n\r\n\r\nEnvironment data\r\n----------------\r\n\r\n```powershell\r\nPowerShell Core v6.0.1 on macOS 10.13.3\r\nPowerShell Core v6.0.1 on Ubuntu 16.04.3 LTS\r\nPowerShell Core v6.0.1 on Microsoft Windows 10 Pro (64-bit; v10.0.15063)\r\nWindows PowerShell v5.1.15063.674 on Microsoft Windows 10 Pro (64-bit; v10.0.15063)\r\n```\r\n","author":{"url":"https://github.com/mklement0","@type":"Person","name":"mklement0"},"datePublished":"2018-03-02T14:32:04Z","url":"https://github.com/PowerShell/PowerShell/issues/6292"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:a8a34fb2-825d-1fc5-c22c-be0f71f35e88 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 95F2:2EC4E1:1DEE13:28907C:6AFD500D |
| html-safe-nonce | 1509341ae2e90863b695e594a365608f041ea7d0c84a21107142db522d839aac |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5NUYyOjJFQzRFMToxREVFMTM6Mjg5MDdDOjZBRkQ1MDBEIiwidmlzaXRvcl9pZCI6IjQxMzg5NDQ2ODEyMzMxNjIzNyIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 1fe4db122a3805c893707142d716831ec4ce7abd979befc5f7b427af0bb53096 |
| hovercard-subject-tag | issue:301784855 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/PowerShell/PowerShell/6292/issue_layout |
| twitter:image | https://opengraph.githubassets.com/5a2593dac1730cc46bd373dd7df22962990503c54adc39df4cc0ea425e722990/PowerShell/PowerShell/issues/6292 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/5a2593dac1730cc46bd373dd7df22962990503c54adc39df4cc0ea425e722990/PowerShell/PowerShell/issues/6292 |
| og:image:alt | Related: #6291 and #6360 Note: Unlike the linked issues, the broken behavior described here only affects PowerShell commands, not also native executables. Steps to reproduce # Basic function withou... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | mklement0 |
| hostname | github.com |
| expected-hostname | github.com |
| None | 66653c2e55a6fff2930be1bdf07ee4f8aa137e3956d056c822563be6f878755e |
| turbo-cache-control | no-preview |
| go-import | github.com/PowerShell/PowerShell git https://github.com/PowerShell/PowerShell.git |
| octolytics-dimension-user_id | 11524380 |
| octolytics-dimension-user_login | PowerShell |
| octolytics-dimension-repository_id | 49609581 |
| octolytics-dimension-repository_nwo | PowerShell/PowerShell |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 49609581 |
| octolytics-dimension-repository_network_root_nwo | PowerShell/PowerShell |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | b6f01f7cb9f35f8c09949773241a3d49dd04b340 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width