Mention null field names #1252
Merged
Mention null field names #1252
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Having a field name expression evaluate to null seems to remove the field from the object. It's a very useful feature so document it in the language spec so that we can rely on the behaviour for any implementation of jsonnet.
johnbartholomew
force-pushed
the
null-field
branch
from
1c46092 to
8aedd19
Compare
Collaborator
|
Thanks for the contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Having a field name expression evaluate to null seems to remove the field from the object. It's a very useful feature so document it in the language spec so that we can rely on the behaviour for any implementation of jsonnet.