You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Something else we could get with ids on code blocks (see #155) is linking between functions in docstrings and comments. Something like:
;; This is a function that calls [[foo/bar]], and does stuff
(defnstuff []
"And a docstring about calling [[foo/bar]]..."
(foo/bar"stuff"))
That would I think be pretty slick, and useful. I realize this could be a bit more challenging than #155 and #156 depending on how the markdown is getting processed. Would probably have to be some pre-processing step.
The text was updated successfully, but these errors were encountered:
I'm working on pyccoon (https://github.com/cryptonomicon314/pyccoon), a fork of pycco, which, like marginalia, is a python fork of docco.
Pyccoon, unlike Marginalia, is set to support multiple languages, although how well each language is supported deppends on the authors.
While I'm not the project's maintainer, I've been working on integrating with clojure, which on my branch is the most well supported language. It features:
Links to definitions in the source (it is not yet namespace aware, but will be soon)
Automatic links to function definitions, both on the same file, on different files in the same project and from external packages (on https://crossclj.info/).
My python code has only the most superficial understanding of clojure, but with a little help from the user and some curated package data (to map from namespaces to package names) I can get pretty cool results.
Much of the new functionality is not yet documented, but I would like your feedback on the output. This is the result of running pyccoon on a slightly customized version of the re-frame package.
The source is hyperlinked (although the links have no special formatting), so feel free to explore and click around.
Major bug: the links don't handle (:require namespace :exclude [...]) directives very well yet.
Something else we could get with ids on code blocks (see #155) is linking between functions in docstrings and comments. Something like:
That would I think be pretty slick, and useful. I realize this could be a bit more challenging than #155 and #156 depending on how the markdown is getting processed. Would probably have to be some pre-processing step.
The text was updated successfully, but these errors were encountered: