-
-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
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
[Feature] Handle with not existing keys #1948
Comments
Hi @xxxcoltxxx, thanks for filing this and thanks for the PR. This has come up before, in #310 and #1362 at least, and I think in other issues as well. I'm not sure why a flag didn't occur to me for controlling it, but at this point it seems reasonable. |
Is there any update on this? I hope this one makes it to a release soon, kinda need it. |
@gjrtimmer thanks for prodding - the PR is stuck, I will unstick it. As for a release, this will be in v4, which won't be "soon" (depending on what "soon" means to you). In the meantime, there are workarounds (the |
Fixed by #1949 |
Hello!
It would be nice to handle non-existing keys.
It will provide flexible control when working with non-existent keys and will make the template more readable.
It allows as to control where we should fallback to some default value and where we should fail template rendering.
Its easy to implement - just add command-line flag that controls the
missingkey=error|zero
option.Current behavior:
Proposed behavior:
The text was updated successfully, but these errors were encountered: