Open
Conversation
Forcing the output to string where freemarker can see it as bool, eg. "true" or "false", forcing it to a string seems safe at the location in the template. This will solve the issue I encountered (issue 8)
|
@perwendel any updates on this? |
|
http://freemarker.org/docs/ref_builtins_boolean.html It seems I think the right fix may be to set the boolean_format setting at the top of the template: |
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
3 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.
Forcing the output to string where freemarker can see it as bool, eg. "true" or "false", forcing it to a string seems safe at the location in the template. This will solve the issue I encountered (issue #5 ). However a review might be good ;), haven't gone to all possible values that can happen at that point.