Fork me on GitHub
#cljdoc
<
2019-10-17
>
wilkerlucio13:10:03

@seancorfield I was thinking about auto-generated, and maybe no curation needed, but I think its a interesting piece of information, if a library or something designs a lot around namespaced keywords, seeing them can give another dimension of understanding about what kind of things flow around the system, makes sense?

martinklepsch13:10:48

I’ve been wanting to integrate something in that direction for a while but reading specs from library sources in the shape we need hasn’t been easy (mostly due to lack of metadata), as far as I understand this will be addressed with spec 2…

jaihindhreddy14:10:28

Programmatic construction and manipulation of specs is improving a lot, but still no ability to attach metadata directly to specs as of yet.

jaihindhreddy14:10:39

Seems to be out of scope for the initial "launch" of spec (the non-alpha version).

martinklepsch15:10:18

@jaihindhreddy we mostly care about basic metadata like file it was defined in and line numbers. See https://github.com/cljdoc/cljdoc/issues/67 for some more context