Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Comparison helpers should still execute when their key parameter is set ... #105

Merged
merged 2 commits into from
Nov 20, 2014
Merged

Comparison helpers should still execute when their key parameter is set ... #105

merged 2 commits into from
Nov 20, 2014

Commits on Nov 18, 2014

  1. Comparison helpers should still execute when their key parameter is s… 

    …et but resolves to undefined.

Previously, if a helper's key parameter was set, but the Dust variable to which it pointed did not exist, the helper would immediately abort. However, this breaks cases especially for {@ne} in which it would be completely valid if the key did not exist.

The helper will still fail to execute if a key parameter is not passed. However, if the parameter resolves to an undefined variable, it will now execute.

This is a non-backwards-compatible change. Closes LinkedInAttic#59.
    Seth Kinast committed Nov 18, 2014
    Configuration menu
    Copy the full SHA
    b27c30a View commit details
    Browse the repository at this point in the history

Commits on Nov 20, 2014

  1. Cleanup syntax in coerce()

    Seth Kinast committed Nov 20, 2014
    Configuration menu
    Copy the full SHA
    5f4c276 View commit details
    Browse the repository at this point in the history