Open
Conversation
Fixes jasonmoo#7 Any value tag can be followed by the name of one or several functions to process the raw value into a form suitable for display. Contains source, modified Readme and test.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Provides an option to add formatters to value outputs.
It doesn't really make sense to pre-process the values with its formatted version just before the template. That would require to make a full copy of an entire table, with the memory and processing resources it takes, when it can really be processed on-the fly while it is being interpolated into the template.
It also allows for some fancy processing as shown in the last test in the test suite below where the render function itself is the formatter, allowing for the recursive processing of a tree-like data structure of an indeterminate depth.