Joe Wicentowski
Joe Wicentowski
As noticed by @dizzzz and me, xqlint parsing errors still will prevent eXide from even executing xqsuite tests via the "XQuery > Run as test" menu. I have a very...
@dizzzz I understand from our conversation in Slack that the https://github.com/joewiz/eXide/tree/disable-xqlint-for-xqsuite branch isn't making the xqlint-for-xqsuite problem go away. Could you please post a link to the test module you're...
@dizzzz Your test works for me in eXide, built from my branch. I copied and pasted your query into eXide, saved it as /db/test.xq, and then selected XQuery > Run...
Another totally valid approach to running xqsuite tests in eXide (or anywhere) is to invoke the xqsuite module manually. All you have to do is write a query like this:...
@ccheraa @plutonik-a While some of the original tests given here do now pass, the issue can still be triggered if you use syntax that xqlint chokes on. For an example,...
@marmoure A simpler test xqsuite module to reproduce the same issue: ```xquery xquery version "3.1"; module namespace t="http://exist-db.org/xquery/test"; declare namespace test="http://exist-db.org/xquery/xqsuite"; declare variable $t:foo := ``[foo]``; declare %test:assertEquals("foo") function t:simple-test()...
@ccheraa I see you mentioned this issue in a comment on a PR submitted to a forked copy of this repository: https://github.com/evolvedbinary/eXide/pull/1. Is that PR part of the fix to...
As discussed and noted in #529, that PR was an important but partial fix. A full fix to this issue requires updating xqlint to accept valid XQuery 3.1 syntax.
Unfortunately, after applying these changes and installing the resulting eXide application package, I get an "Uncaught TypeError: Cannot read property 'SemanticHighlighter' of undefined" error in my browser when loading eXide....
It is still a "work in progress." The problem is that xqlint seems to have changed substantially since the time Wolfgang first integrated it into eXide, and I'm unsure how...