Agreed, this behavior is unexpected. I'm not sure though what was the original use case for this behavior. Changing implementation would be backward incompatible. With original implementation we returned false only when output was an empty string. Changing logic to `}else { return dustBodyOutput || false; }` will return false for any falsy value.