Bug - Correct Syntax Throwing Error for non empty value in context

[satyajitnayk]

Syntax

{{#if (name)}}{{/if}}

Throw Error When pass non empty string for name in context

Empty value for name in context	Non Empty value for name in context

Error String

   (lookupProperty(...) || (depth0 && lookupProperty(...)) || container.hooks.helperMissing).call is not a function
    

    Error: (lookupProperty(...) || (depth0 && lookupProperty(...)) || container.hooks.helperMissing).call is not a function
    at t._callbacks.<computed> (https://handlebarsjs.com/assets/js/8.214167ea.js:1:61688)
    at n (https://handlebarsjs.com/assets/js/8.214167ea.js:1:61432)
    at Worker.<anonymous> (https://handlebarsjs.com/assets/js/8.214167ea.js:1:61536)

Same Happening for unless helper too

[tiholic]

I too faced the same issue

[satyajitnayk]

Same is observed in other helpers too . This should be addressed as soon as possible as it could cause severe issue for whoever is using handlebars in production. Thoughts @jaylinski ?🤔

For example lookup helper

Same Error when there is non empty string in merge key:

No Error when merge context key is empty string:

[mohd-akram]

Do not wrap name in (). Parentheses are for sub-expressions. See the documentation.

[satyajitnayk]

Parser should throw error for syntax itself right?
but it is not doing so & only throwing at compilation with merge context!