We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug I think this change happened in #922.
For example, given yaml like:
foo: bar: null
and CEL like:
foo.?bar.?baz.orValue("not there")
behavior changes from returning "not there" to throwing a no such key error.
To Reproduce Check which components this affects:
Expected behavior Expected "not there" to be returned.
Additional context
I tried reverting the change from #922 and it makes things work the way I expect.
The text was updated successfully, but these errors were encountered:
Thanks for the report. I'll give it a look.
Sorry, something went wrong.
TristonianJones
Successfully merging a pull request may close this issue.
Describe the bug
I think this change happened in #922.
For example, given yaml like:
and CEL like:
behavior changes from returning "not there" to throwing a no such key error.
To Reproduce
Check which components this affects:
Expected behavior
Expected "not there" to be returned.
Additional context
I tried reverting the change from #922 and it makes things work the way I expect.
The text was updated successfully, but these errors were encountered: