I missed the obvious part of option 'suboptions'
I fixed the parsing in basex-stream and now `query.options()` returns an
object in v0.1.2.
The behavior is correct indeed. But I agree it is surprising, and it
has not properly been documented so far:
> declare option output:json "lax";
This is a shortcut for "lax=true". Thus, the boolean value will always
be appended in the string representation, no matter if it has been
specified in
Hi,
While testing for basex-stream i encountered a weird behavior
in the OPTIONS query command.
After creating the query
```xquery
declare option output:method "json";
declare option output:json "lax";
```
the response of OPTIONS was:
`json=lax=true,method=json`
Which seems wrong.
I event
3 matches
Mail list logo
