First of all, I have to say that I liked this plugin, to the extent that now I am facing minor issues, and I want them to be resolved. Appreciate your help.
The following cases are causing incorrect parsing:
1- A missing semicolon in JavaScript source will cause SourceCookifier to mis-parse the code parts that follows this statement:
I notcied, after detailed search, that if there is a missing semicolon ";" that terminates the JavaScript statement, this will cause misparsing (incorrect parsing) for the following code parts. The problem is minor, but causes the "go to definition" feature using "ctrl-shift-enter" not to work at all for some functions.
See attached file "test.js" which will reproduce the problem.
2- If you define a variable as array of objects, then this variable will not show in the tree view panel on the right-side, under global variables.
First of all, I have to say that I liked this plugin, to the extent that now I am facing minor issues, and I want them to be resolved. Appreciate your help.
The following cases are causing incorrect parsing:
1- A missing semicolon in JavaScript source will cause SourceCookifier to mis-parse the code parts that follows this statement:
I notcied, after detailed search, that if there is a missing semicolon ";" that terminates the JavaScript statement, this will cause misparsing (incorrect parsing) for the following code parts. The problem is minor, but causes the "go to definition" feature using "ctrl-shift-enter" not to work at all for some functions.
See attached file "test.js" which will reproduce the problem.
2- If you define a variable as array of objects, then this variable will not show in the tree view panel on the right-side, under global variables.
Tarek
Last edit: Tarek Faham 2018-09-06
I am still suffering from this issue. Can you please check it out and let me know when you can resolve it?