No visual error for undeclared variables in a for each child event [solved, in the queue]

I don’t know if this is a bug or a feature but…

Undeclared variables you use with a for each child variable event don’t get underlined or displayed in red. This makes it difficult to tell if the variable exists.

The variables Qwerty and child don’t exist but they aren’t underlined or displayed in red like in the following event.

It’s very easy to type the wrong variable name. It can be misspelled or simply have letters in the wrong case. It’s also possible to delete a variable and not see a visual clue that the variable isn’t defined.

3 Likes

We can’t fix it until every templates are migrated to declared variables or they would appear in red. So it will take a while.

2 Likes