You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
jgresham
changed the title
Differences in how "defaultConfig" and "defaultValue" is used
[controllers aka node specs] Differences in how "defaultConfig" and "defaultValue" is used
Aug 1, 2024
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'defaultValue
s 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 adefaultValue
under the specific config.The text was updated successfully, but these errors were encountered: