doctree

Another issue with tree-sitter is how basic functionality is not consistent across all languages. Want to find all comment text in all languages? Each tree-sitter lang support will have a slightly different behavior for every language. When you extract the comment you'll have syntax from the language in there like `/*/` or `{}`. Example from a sourcegraph docs generation project: https://github.com/sourcegraph/doctree/blob/07a2d593fe9855be... https://github.com/sourcegraph/doctree/blob/07a2d593fe9855be...

Quite a lot, actually! It's definitely not ready for prime-time usage or anything, but I feel good about the week of time on it: * There are some Docker commands you can use to try it out on some Go code right now[0] (still working on getting binary releases for each OS so Docker is not necessary) * There's a not-too-bad frontend (written in Elm), screenshots in the README are real & it all functions! * There's an indexer implemented for the Go language[1] that runs tree-sitter queries & emits a basic schema[2], the idea is each language would emit to a common schema like this and then the frontend can serve it, we can index it for search, etc. So, I mean, yeah - just a week into it, but like - you can already view documentation for Go functions in it so moving quickly! [0] https://github.com/sourcegraph/doctree#try-it-out-extremely-... [

Whoa, wasn't expecting to see this on HN! I've only done a week of work on this, super early stages - here are our plans for it: * 100% OSS tool, run locally on your machine (static Go binary) or use https://doctree.org (not online yet, plug in a repository name, get docs) - really want this to be a proper, useful FOSS tool. * Work with any language, based on tree-sitter. * Provide symbol-level search functionality. * Surface real-world usage examples automatically, probably based on some statistical analysis of how functions are commonly used in open source code via Sourcegraph API, similar to what https://codestat.dev is doing. Tech details (again, just a week in): * Go for backend, Elm for frontend * Indexers will be written in Go, use tree-sitter queries to produce a standard index schema which then gets served to Elm frontend for ren