Daniel Compton

One note for people following along, the @v1 tag currently doesn’t include OIDC support, even though the docs say to use @v1. You’ll either need to pin to a recent...

Spitballing a few paths you could go down with this idea: * Create a `.config/cljdoc/` directory which can contain one or more files with cljdoc config. * Create a `.cljdocignore`...

> * Maybe this is something we can read from the Jar or POM file Inside the JAR is a `MANIFEST.MF` file. You can pull it out with ```console $...

If you have SCM information then you could work out the date of the commit that the JAR was built from. That's not exactly the same thing, but is probably...

If I get the chance I will make a PR, but happy for you to do it if you get to it first :)

Heh, yeah spec was definitely on my mind. I haven't seen many libraries shipping spec annotations yet as it's still in alpha, and with spec-alpha2 around the corner I'm not...

One thought I had on this is that the feature files will need to come from source control (like some other docs already) as they normally wouldn't be shipped in...

FWIW, I really like that printing is only shown in failing test cases, though I can see how people could get confused by that. Another idea would be to print...

It seems like constraining the instrumentation to just Kaocha's namespaces could be a good option here to avoid causing problems for application test code. This would get you a collection...

Here's the solution I came up with. It's pretty dirty, but seems to work ok. I'd love to know of a better way though. ```clj (ns my.app.db.queries (:require [my.app.vendor.hugsql.core :as...