René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Tab-completion doesn't honor the provider context provided by a previous argument when surfacing dynamic parameters","articleBody":"### Prerequisites\r\n\r\n- [X] Write a descriptive title.\r\n- [X] Make sure you are able to repro it on the [latest released version](https://github.com/PowerShell/PowerShell/releases)\r\n- [X] Search the existing issues.\r\n- [X] Refer to the [FAQ](https://github.com/PowerShell/PowerShell/blob/master/docs/FAQ.md).\r\n- [X] Refer to [Differences between Windows PowerShell 5.1 and PowerShell](https://docs.microsoft.com/powershell/scripting/whats-new/differences-from-windows-powershell).\r\n\r\n### Steps to reproduce\r\n\r\n\r\n```powershell\r\nPush-Location function:  # change to a non-file-system location\r\n(TabExpansion2 'Get-ChildItem -LiteralPath $PSHOME -Fi').CompletionMatches.ListItemText\r\nPop-Location\r\n```\r\n\r\n\r\n### Expected behavior\r\n\r\n```console\r\nFilter\r\nFile\r\n```\r\n\r\n\r\n### Actual behavior\r\n\r\n```console\r\nFilter\r\n```\r\n\r\nThat is, even though the file-system provider is implied by the `-LiteralPath` argument, tab-completing `-Fi` didn't surface the dynamic `-File` parameter.\r\n\r\n\r\n### Error details\r\n\r\n_No response_\r\n\r\n### Environment data\r\n\r\n```powershell\r\nPowerShell Core 7.4.0-preview.2 (behavior dates back to Windows PowerShell)\r\n```\r\n\r\n\r\n### Visuals\r\n\r\n_No response_","author":{"url":"https://github.com/mklement0","@type":"Person","name":"mklement0"},"datePublished":"2023-04-12T20:59:42.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/19498/PowerShell/issues/19498"}