Skip to content

Tab-completion doesn't honor the provider context provided by a previous argument when surfacing dynamic parameters #19498

@mklement0

Description

@mklement0

Prerequisites

Steps to reproduce

Push-Location function:  # change to a non-file-system location
(TabExpansion2 'Get-ChildItem -LiteralPath $PSHOME -Fi').CompletionMatches.ListItemText
Pop-Location

Expected behavior

Filter
File

Actual behavior

Filter

That is, even though the file-system provider is implied by the -LiteralPath argument, tab-completing -Fi didn't surface the dynamic -File parameter.

Error details

No response

Environment data

PowerShell Core 7.4.0-preview.2 (behavior dates back to Windows PowerShell)

Visuals

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    In-PRIndicates that a PR is out for the issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions