dotnet/command-line-api

Tab completion is not triggered for dotnet-* commands when invoked with a space after dotnet

Open

#343 opened on Dec 20, 2018

View on GitHub
 (2 comments) (0 reactions) (0 assignees)C# (3,665 stars) (421 forks)auto 404
Area-Completionsbughelp wanted

Description

Tab completion for "dotnet"-prefixed global tools works when invoked like this:

dotnet-something ⇥

It does not work when invoked like this:

dotnet something ⇥

This fix should be made for both:

  • bash
  • PowerShell

Contributor guide

Tech stack
shell
Domain
cli
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Knowledge of bash completion scriptsKnowledge of PowerShell completion scripts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The issue describes that tab completion for dotnet prefixed global tools works for 'dotnet something' but not for 'dotnet something'. The fix involves modifying the completion scripts for bash and PowerShell in the repository. Look for the completion script files (likely in src/ or scripts/ directories) and update them to handle the 'dotnet' subcommand style. Refer to existing completion logic for dotnet something as a template.