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
Orquesta/Jinja/YAQL currently throws an error when you try to use a key that does not exist:
"YaqlEvaluationException: Unable to resolve key 'result' in expression '<% result().result.output %>' from context."
But this leaves you guessing as to what valid keys you can use.
It would greatly ease workflow development if we dumped a list of valid keys in the error message:
"YaqlEvaluationException: Unable to resolve key 'result' in expression '<% result().result.output %>' from context; must be one of 'option1', 'option2', or 'option3'."
But if we want to avoid l10n/i18n issues with lists (I'm also not sure we handle this at all), we can also simply dump an array of options:
"YaqlEvaluationException: Unable to resolve key 'result' in expression '<% result().result.output %>' from context; must be one of ['option1', 'option2', 'option3']."
The text was updated successfully, but these errors were encountered:
Orquesta/Jinja/YAQL currently throws an error when you try to use a key that does not exist:
But this leaves you guessing as to what valid keys you can use.
It would greatly ease workflow development if we dumped a list of valid keys in the error message:
But if we want to avoid l10n/i18n issues with lists (I'm also not sure we handle this at all), we can also simply dump an array of options:
The text was updated successfully, but these errors were encountered: