Allow filters to be used to set default values when a key is falsy #27
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.
Commit msg:
Modified the return value of Context.reference to allow filters to be used to set default values
Reason
When working with JSON api responses sometimes a section of the data structure might be empty and undefined, by default dust will not render anything for these missing keys, so this changes allows for the use of filters to fill in the blanks. Lets say we have a data structure of statistics, some stats are n/a so they are undefined. Using a filters like so:
We can make sure that the undefined numerical values come up as 0s or any other default value desired.