Skip to content

Displaying help after parse error reporting should be configurable #2191

Open
@KathleenDollard

Description

@KathleenDollard

The Cli author, or better yet the end-user via an environment variable, should determine whether to display help after parse errors.

I hate that behavior with a passion because of how often it leads to scrolling to see the parse error. If I want help, I will ask for it. I never want to see it on errors.

(This is from seeing the code in ParseErrorAction.

Activity

baronfel

baronfel commented on May 10, 2023

@baronfel
Member

Big 👍 on this one - the dotnet CLI has overridden parse error reporting to only conditionally show the usage for this reason. It's possibly related to/dependent on the length of the usage section.

KalleOlaviNiemitalo

KalleOlaviNiemitalo commented on May 10, 2023

@KalleOlaviNiemitalo

Related #1873 and #1214

jonsequitur

jonsequitur commented on May 10, 2023

@jonsequitur
Contributor

I'm working on this currently as part of the next round of CliAction improvements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @jonsequitur@baronfel@KathleenDollard@KalleOlaviNiemitalo

        Issue actions

          Displaying help after parse error reporting should be configurable · Issue #2191 · dotnet/command-line-api