You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Information in the module such as functions that follow the error is not processed -- this causes calls to those functions to be incorrectly reported as errors.
Automatic indentation is broken when entering code after the point of the error.
It would be helpful for the parser to recover as close as possible to the next valid start/recover point. I understand that this will be complex.
At the basic level, this should be able to recover to the start of the next statement such as if, for, let, and declare function statements.
The text was updated successfully, but these errors were encountered:
Unfortunately with the very context-sensitive nature of the language and with the fact that in Main Module you can have any expression at the end of the file, it's nearly impossible to get this done right.
If you could please prepare some examples with the expected behaviour it would be much easier to at least check if this is achievable.
declare function a($x, $y) {
if ($x < (2*$y)) then
$y
else
$x
};
declare function b($x) {
()
};
Here, the code in the $x and $y part of the if will not be validated, and function b will not be exposed to the user when referring to it in another module.
If the intellij-xquery parser encounters an error, the code that follows the error point is not parsed correctly. This has the following effects:
... < (...)
are reported as errors. #198).It would be helpful for the parser to recover as close as possible to the next valid start/recover point. I understand that this will be complex.
At the basic level, this should be able to recover to the start of the next statement such as
if
,for
,let
, anddeclare function
statements.The text was updated successfully, but these errors were encountered: