GitHub Community
Guide for how language communities can self-serve language support? #10934
-
|
Hi! I've been enjoying using Github Code Search so far. I'm part of the Dart language team (https://github.com/dart-lang) and we would love to add Dart support for Github Code Search.
In the announcement about precise code navigation it's stated:
I was wondering if that guide has been published yet? Or if not, I wanted to verify that if we add Tree-sitter support for Dart, the Github team would be able to add symbol extraction in Code Search and in the regular Github code UI? (Since stack-graphs builds off of the Tree-sitter parsers this seems like a reasonable first step). Thank you! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
For code search, if you implement a tree-sitter parser for Dart, we can absolutely enable things like fuzzy jump-to-definition and better ranking. That would be awesome! We can do it pretty quickly, just let us know when you have a parser. Getting "precise" stack graph support is a bit more complex, as it's more than just a parser. But we want to enable third parties to help us with that too, I'll let @dcreager answer that one. |
Beta Was this translation helpful? Give feedback.
-
|
Hi there! Yes as @colinwm mentioned, the first step is to get a tree-sitter parser that you're happy with, including syntax highlighting and symbol tagging queries. That will be enough for us to support Dart in Code Search, Fuzzy Code Nav, and Syntax Highlighting. (Dart is already a syntax-highlighted, but uses an old highlighting engine based on regular expressions. As part of adding support for Code Nav and friends, we typically migrate the language over to our new parser-based highlighting engine.) For stack graphs, we still haven't published a proper guide yet, but the tree-sitter-graph and stack-graphs repos are the best place to follow our progress. The tl;dr is that we've created a new "graph construction DSL" for tree-sitter, which lets you create the necessary stack graph structure from the parsed syntax of the language. (If you haven't seen it yet, I go into some initial detail about that process towards the end of my Strange Loop talk from last fall.) Those two repos are where that logic will live — we are migrating an internal version of that DSL over to the externally visible tree-sitter repos. Re timing, my hope is that if you all are able to make progress on the Fuzzy Code Nav side, by the time that is done we will hopefully be ready to work with some initial language communities to walk them through the process of writing stack graph rules. So first steps are right in line with what @colinwm said — let's get a Dart grammar squared away with highlighting and tagging queries in it. |
Beta Was this translation helpful? Give feedback.
-
|
Great, thanks for all this great information! Will circle back around once we have a tree-sitter parser. |
Beta Was this translation helpful? Give feedback.
For code search, if you implement a tree-sitter parser for Dart, we can absolutely enable things like fuzzy jump-to-definition and better ranking. That would be awesome! We can do it pretty quickly, just let us know when you have a parser.
Getting "precise" stack graph support is a bit more complex, as it's more than just a parser. But we want to enable third parties to help us with that too, I'll let @dcreager answer that one.