Gonna try placing the new assertion in a more adequate test file.

Waiting for confirmation from @bobthecow, just in case: https://twitter.com/dasilvacontin/status/709796886568423424.

This is probably in the category of things — like the definition of "falsey" — that is up to the individual library to decide what best fits in the host language. In my opinion the JavaScripty thing to do when encountering a null is to treat it as "the user intentionally put nothing here", and thus to interpolate it as an empty string. This is what Mustache.php does as well:

Note that null in a block context will also stop context stack lookups from propagating.

At the very least, if I'm wrong it'd be a backwards compatibility break, so it's not allowed until the next major release :)

In my opinion the JavaScripty thing to do when encountering a null is to treat it as "the user intentionally put nothing here", and thus to interpolate it as an empty string.

Note that null in a block context will also stop context stack lookups from propagating.

Thanks for your insight! We are doing both things – great! 😄. We treat null as a marker for "nothing" (which is what null really is), so:

• the lookup function stops and returns null when it finds it (we fixed some edge-cases regarding this behaviour not long ago),
• it's considered as falsy for blocks, and
• it's currently being rendered as an empty string. 😄

👍 sgtm