Skip to content

[controllers aka node specs] Differences in how "defaultConfig" and "defaultValue" is used #639

@jgresham

Description

@jgresham

Problem details

When setting execution.input.defaultConfig it forces those values to be used on the run command anytime before the user has "saved" from the node settings modal. After the user has saved from the node settings modal, ALL of the configs' defaultValues are included in the run command.

This shouldn't cause any issues, but it does mean that there are a bunch of additional default value cli input after the users saves the settings (doesn't even have to make a change to any of them). It also means that we have to explicitly include default config that should be used on every run command in 2 places execution.input.defaultConfig and as a defaultValue under the specific config.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions