Conditional expressions without operators don't work properly (linq.ts BUG)

[jure123]

I found that linq.ts -> expressionParser() function has a bug with boolean expressions that don't use operators.

This conditional expression in @disable decorator does not work propery:

@disable({conditionalExpression: function () { return this.isChecked; }})
--> In this case linq espressionParser() extracts colum name "isChecked;" with included semicolon at the end which does not work

But it works if we put "== true" to the right side of the expression:
@disable({conditionalExpression: function () { return this.isChecked == true; }})
--> In this case linq espressionParser() extracts colum name "isChecked" (without semicolon which if correct of course)

You can try my example on stackblitz (clicking the button should toogle disable of textbox, but it does not work unless you append "== true" to the conditional expression:

https://stackblitz.com/edit/angular-z5p584?file=src%2Fapp%2Fuser.model.ts

BTW: The example below also does not work:
@disable({conditionalExpression: function () { return this.isChecked }})

I have removed the semicolon at the end of expression but the linq parsers still extracts column name "isChecked;" with semicolon (probably somewhere the code automatically adds semicolon to the end of expression)

@rxweb/reactive-form-validators 2.1.4

[ajayojha]

@jure123 Thanks for reporting this. This is a known issue and we have mentioned a note in most of the conditional expression example documentation, but missed on the disabled example.
Here is the note, like:

I keep this ticket in the open state, but no chance to fix this soon, as we have the alternative to work with conditional expression :).

[jure123]

@ajayojha, thanks for your info. Indeed it is no big deal because we have a simple workaround :)

[timrasche]

+1