Skip to content

Conversation

@jlcrochet
Copy link

@jlcrochet jlcrochet commented Jan 7, 2026

This new static completions provider makes use of NuShell's extern to define completions for dotnet commands. Similarly to the other shell providers it falls back to dotnet complete in cases where dynamic completion of option values is needed.

asciinema example usage: https://asciinema.org/a/wFSDtsB2eui8JsUe

Attached is what the output of dotnet completions script nushell looks like.

dotnet-completions.txt

@jlcrochet

This comment was marked as off-topic.

@baronfel
Copy link
Member

baronfel commented Jan 7, 2026

@jlcrochet This is awesome, THANK YOU for taking the time to do this. Would it be possible to get something like an asciinema recording/gif of the completions working and what the experience looks like for those of us without nushell?

@jlcrochet
Copy link
Author

I edited a link to the asciinema in the original comment.

@jlcrochet jlcrochet marked this pull request as draft January 9, 2026 09:12
It seems that descriptions for argument and option
values don't display if the completion list is
inlined, so we have to generate completion
commands for these.
In the case where we use sentences for
descriptions, strip the period off the end for
consistency.

In the case where we use the first line of a
description, we should *not* use it if it ends
with a punctuation character indicating the
beginning of an overly complex description.
@jlcrochet jlcrochet marked this pull request as ready for review January 10, 2026 00:42
@jlcrochet jlcrochet marked this pull request as draft January 10, 2026 05:28
@jlcrochet jlcrochet marked this pull request as ready for review January 10, 2026 08:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants