Typically I would recommend a bite size step by step code inclusion/conversion of java to JavaScript so that debugging is targeted, so as to ease progression.
Lint is a code analysis tool used for checking if JavaScript source code complies with coding rules and best practice. For example, it is best practice to end a JavaScript statement with a semicolon the syntax does not require it.
The lint checker flags code the uses of the JavaScript eval function as a potential security threat. It is unlikely that this is the case when evaL is used to parse user-entered functions, but the lint program does not know how eval is being used and issues the warning. See the Stack Overflow discussion about the use of eval in JavaScript.
It occurred to me: something isn't making sense: the lint checker messages that I see are for EJsS code, not for code that I wrote. That is, the messages are about EJsS internals, and it makes no sense for them to be displayed in an end user panel.
(See the attached screenshot)
The source of the lint checker messages is unclear.
Oracle has swapped out Javascript engine twice. There was a move to the Nashorn javascript engine, and later a move to the GraalVM. (I'm using Java 8) I don't know whether any of this is relevant. But the general impression I get that with Java under Oracle stewardship Java is becoming a moving target.
So my best guess is that displaying those lint checker messages is accidental, not intended.
I remember Paco mentioning that he has Windows running in a Virtual Machine, to test Windows environment. I suppose that the lint checker messages did not and do not appear in Paco's testing setup.
