StackStorm / StackStorm/orquesta
"ExpressionEvaluationException: Unable to resolve key" error should include list of available keys
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 111
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
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']."
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Orquesta/Jinja/YAQL evaluation path that raises the unresolved-key error, then find the existing tests for that error. Done means the error reports the available keys in a stable format and the behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100