Handle empty strings #26
Merged
Conversation
This file contains 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
curran
approved these changes
Nov 1, 2018
|
That was fast, thanks a lot! |
|
I just realised I missed a semicolon at the end of this line. I'm not gonna open a new PR just for that, but next time you get around committing some changes... 😉 |
|
Fixed. Thanks! d9cd78e |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi,
I noticed that the templating system seems to be having issues with empty strings (and other values resulting in
if (value)evaluating tofalse) as parameter values:parse('{{foo}}')({ foo: '' })returnsnull(in fact, thedefaultValue) instead of''I added a test for this edge case, and fixed it.
Tell me what you think 🙂
Cheers,
Flo