Skip to content

System.CommandLine is split into too many namespaces  #1680

@jkotas

Description

@jkotas

I end up writing the following battery of namespaces into every project:

using System.CommandLine;
using System.CommandLine.Builder;
using System.CommandLine.Invocation;
using System.CommandLine.Parsing;

Should these namespaces be all folded into one?

This design is in conflict with .NET Framework design guidelines:

AVOID having too many namespaces.

Users of a framework should not have to import many namespaces in the most common scenarios.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions