Skip to content

Make type mandatory for configured options #94

@bakkot

Description

@bakkot

@bcoe suggested this here. I'm in favor of it, and wanted to open an issue for it so it doesn't get lost.

This would definitely apply to strict. I don't know if it should also apply to non-strict. I'm still not entirely clear on what non-strict is for, which makes it hard to judge what's right for it.

I note that if if type is not required for non-strict, you have odd cases like

parseArgs({ options: { foo: { multiple: true } }, args: ['--foo', 'a', '--foo'] })

where... would that give you { values: { foo: ['a', true] } }, or what?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions