Martin Klepsch

@hellonico you could open a PR that modifies this line to exclude the `dev` task: https://github.com/jasongilman/proto-repl/blob/8c8886f14a50a4edf205d744a61831f4424dd882/lib/proto-repl.coffee#L44 I'm sure @jasongilman will accept it.

@metasoarous Hi and thanks for the update! There's no way to add a deps.edn alias as the dependency resolution mechanism used in cljdoc solely relies on the `pom.xml` that is...

A bit of an aside but I saw that there's a bit of code in some of the docstrings in the namespace you linked above. Docstrings on cljdoc are interpreted...

> This is maybe a separate issue (happy to raise if you like), but @cnuernber pointed out that a challenge with getting cljdocs up for `libpython-clj` is that some of...

I've been thinking about this issue since it was opened (thanks @urzds). Unfortunately the main cljdoc frontend code simply isn't intended to be rendered to a directory on disk. There...

A nice way to integrate this into people's CI workflow could be by exposing it as a [CircleCI Orb](https://circleci.com/docs/2.0/creating-orbs/). Obviously this will only work for CircleCI :smile:

Now with #263 providing an easy way to generate offline bundles we could package a CircleCI Orb or GitHub Action to do the following: - download cljdoc - ingest a...

I've looked into this a bit more just now. One of the things that's still unclear to me is how/if the orb would have access to the workspace/disk as it...

@danielcompton also not a fan of more stuff in a repository’s root directory 😄 We already have `doc/cljdoc.edn` which we could also use for this purpose. An interesting problem to...

Until this is implemented in a way that allows configuration via `cljdoc.edn` users may open a PR and manually exclude their files by extending this function: https://github.com/cljdoc/cljdoc/blob/cf9f511b78b02667d097d84690a6c0960ac827d3/modules/analysis-runner/src/cljdoc/analysis/runner.clj#L54-L88