If you forget to close a ", ' , ( , [ , { etc the tree-sitter will show a MISSING in the tree. It will show a ERROR in the tree when it can not figure how to parse, and keep on trucking
The parsed #xquery tree should be easy to read. It should not error on valid XQuery syntax, but this does not mean the code will compile. Have a play and see what it is doing.
With the playground you can easily see whats going on in terms of the syntactic structure of you code compared to something like... https://t.co/oVaTRHZ9RI
When #treesitter can not complete an #xquery expression, it keeps on trucking until it finds a expression it can complete. In #neovim the error is underlined so you can see incomplete expressions while typing
This is a stab at providing a #treesitter for #xquery.
At this stage, I am happy with the semantic highlighting it provides in #neovim and open to feedback.
https://t.co/Z3yWmWdalV
xq a terminal cli for #xqerl
Overloaded `xq get {db-uri}` to not only retrieve db items but also drill down using #xQuery#xPath and lookup expressions.
`xq get {db-uri} {lookup}` for maps and arrays
`xq get {db-uri} {xpath}` for document nodes
https://t.co/xLWSngyxpn