Would you be open to me adding an eval on the inputs to custom queries? It would make queries even more flexible.
Here are two examples of custom inputs I’d like to have. Right now, having access to those inputs requires adding new cases to resolve-input, i.e. a full code change. It’d be really cool if it could all just live in the users’ markdown files and be more dynamic!
Yes, we’re open to adding an eval on the inputs to custom queries
To make it really works, we might need to provide some bindings for sci, for example, the util/time-ms, because sci doesn’t have access to this function and runtime vars by default.
Hmmm since it would require providing bindings for sci (something like the below, I presume), that still requires going into the source and actually adding the bindings each time.
This is slightly more flexible than having the pre-defined symbols like :today and :1d-after and that kind of thing, because then you can use them as functions rather than being stuck with whatever arguments the symbols happened to support, but only slightly more flexible.
Do you think it’s worth it to add the eval after all? I lean towards “no”, but I’m on the fence.
Those bindings are mostly related to debugging (e.g, println, pprint) and date/time, right?
How about adding bindings for the debugging functions and several namespaces from cljs-time like this: