We need to be able to differentiate between a nil default value and an empty string default value, for example. This can only be done if we support nil default values. A nil default value means that the user MUST override it when creating a workflow. This is useful when a component requires an API token. Currently we are setting dummy string values for these parameters that a user is easy to miss. These values should be nil by default and the engine should throw an error that identifies exactly which value was not set by the user to make the engine fail faster and in a more clear way.
We need to be able to differentiate between a
nildefault value and an empty string default value, for example. This can only be done if we supportnildefault values. Anildefault value means that the user MUST override it when creating a workflow. This is useful when a component requires an API token. Currently we are setting dummy string values for these parameters that a user is easy to miss. These values should be nil by default and the engine should throw an error that identifies exactly which value was not set by the user to make the engine fail faster and in a more clear way.