Add query namespace support

[mprokopov]

http://etaoin.grishaev.me/etaoin.query.html

It would be nice to have query namespace as well in babashka-etaoin pod.

[borkdude]

Feel free to add

[borkdude]

I'll wait for this one before the next release

[borkdude]

I'm wondering if we should expose this since etaoin has an explicit api and api2 namespace. If these functions are not exposed through the API maybe they are considered to not be part of the API?

/cc @igrishaev

[borkdude]

I haven't had an answer, so I'd say, let's just expose it.

[igrishaev]

Sorry @borkdude I was on my NY holidays. It's OK to expose the query namespace.

[igrishaev]

Actually, the primary namespace in Etaoin is the .api one. The .api2 carries the new versions of macros that cannot be fixed in the .api without breaking the things. The .api namespace requires the .query ns.

[borkdude]

@igrishaev Thank you for the reply! Are you saying that the query functions are available already in the API ns?

[igrishaev]

Yes @borkdude , the .api ns imports the .query: https://github.com/igrishaev/etaoin/blob/master/src/etaoin/api.clj#L23

[borkdude]

Yes, the API namespaces uses the query namespace, but this isn't what I'm asking. I'm asking if it exposes the query namespace. So if you want to use a function from query, is it available via API?

[igrishaev]

Well, it looks like query functions are available only from the .query ns. I'm a bit unsure what does the expose word mean. Did you mean something like:

;; api.clj

(def expand query/expand)
;; and so on?

[borkdude]

Yes, that's what I mean :) If there is an API, I would expect all functions that are intended as the API to be available there, but I could be wrong.

[igrishaev]

Well, it's not so at the moment. Should a user need any of the .query functions, he or she needs to require it manually. Does it cause an issue for the babashka pod?

[borkdude]

No not at all. My only question was: is that etaoin.query namespace intended to be used by library users, given that you also have an explicit api namespace. It seems the answer is still yes. So let's expose it in the pod.

[borkdude]

@mprokopov I added query/expand to the master branch now. Is this the only var you want, or are there more?

[mprokopov]

Looks great, @borkdude!
This is totally enough and thanks for your efforts!

[borkdude]

@mprokopov This is released now as 0.1.0.