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
eXide raises an error whenever the lookup operator is used on maps and arrays, e.g., map { "bar": "baz" }?bar and ["a", "b", "c"]?2. These queries can be submitted and return correctly, so this isn't an eXist error - it's probably an xqlint error. Ever since #529 such errors are prominently displayed in the editor window rather than appearing only in the javascript console.
Expected behavior
eXide should not raise an error when the lookup operator is used.
To Reproduce
Enter a query using the lookup operator into the eXide editor window: map { "bar": "baz" }?bar or ["a", "b", "c"]?2
Same goes for the arrow operator. "foo" => string-length() will generate the same error.
joewiz
changed the title
[BUG] erroneous "lexical error" with lookup operator on maps and arrays
[BUG] erroneous "lexical error" with lookup operator on maps and arrays, etc.
Oct 25, 2022
Describe the bug
eXide raises an error whenever the lookup operator is used on maps and arrays, e.g.,
map { "bar": "baz" }?bar
and["a", "b", "c"]?2
. These queries can be submitted and return correctly, so this isn't an eXist error - it's probably an xqlint error. Ever since #529 such errors are prominently displayed in the editor window rather than appearing only in the javascript console.Expected behavior
eXide should not raise an error when the lookup operator is used.
To Reproduce
Enter a query using the lookup operator into the eXide editor window:
map { "bar": "baz" }?bar
or["a", "b", "c"]?2
eXide will display an error:
Screenshots
n/a
Context (please always complete the following information):
Additional context
conf.xml
? None.The text was updated successfully, but these errors were encountered: