Clojurians Log v2

@drcode Hi, is it by design that only unqualified keywords are possible for custom elements in qlkit-renderer?

I’m working on wrapper for recharts and already have clash with label and legend…

It would be nice if fully qualified keywords were supported

@drcode is qlkit's query compatible with that of om.next?

I mean for server side part

@myguidingstar the syntax is a bit different, the parameters of parser function are a bit different, also you don’t have to return {:value ,,,} just the value itself https://github.com/forward-blockchain/qlkit/wiki/The-Qlkit-Graph-Query-Language

We were able to move our om.next application quite smoothly to qlkit. The complexity is much smaller and hard to fix bugs vanished.

also I think qlkit doesn't support union queries