Skip to content

InputMerger not merging options with defaults properly #75

Closed
@tomzx

Description

@tomzx

It appears that if an option with InputOption::VALUE_NONE is not set, its default value is false. This in turns, mean that when we merge the input into the configuration, the false value overrides whatever value was set for that option.

Edit: After thinking about this issue for a bit, I've realized that this can be generalized to the fact that we will be unable to properly merge the command line options if they have default values other than null since InputMerger relies on them being null by default to decide if they should take the value of the configuration (if any).

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions