srctx
lsif-go
| srctx | lsif-go | |
|---|---|---|
| 4 | 6 | |
| 31 | 114 | |
| - | - | |
| 8.8 | 10.0 | |
| 5 months ago | 8 months ago | |
| Go | Go | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
srctx
- Visualize Your Commits: Automatically Evaluate Function-Level Impact in Seconds with a simple setup. Cross-Language. (https://github.com/williamfzc/srctx)
-
srctx: A golang library for automatically evaluating the function level impacts of Git Diff
wget https://github.com/williamfzc/srctx/releases/download/v0.4.2/srctx-linux-amd64 chmod +x srctx-linux-amd64 ./srctx-linux-amd64 diff --before HEAD~1 --after HEAD --lsif dump.lsif --outputCsv output.csv --outputDot output.dot ```
- srctx: a LSIF parser for understanding what happened in every lines of your code
- Enhance git diff with LSIF
lsif-go
-
srctx: A golang library for automatically evaluating the function level impacts of Git Diff
curl -L https://github.com/sourcegraph/lsif-go/releases/download/v1.9.3/src_linux_amd64 -o /usr/local/bin/lsif-go chmod +x /usr/local/bin/lsif-go lsif-go -v
-
Codegraph – static code analyzator / code diagramer
Very nice. For those interested, you can get similar information using SourceGraph and LSIF in a standardized, language agnostic form: https://lsif.dev/. It still generally requires build information for each project/language, unfortunately.
- srctx: a LSIF parser for understanding what happened in every lines of your code
- Steve Yegge Joins as Head of Engineering of Sourcegraph
-
“Zoom Out”: The missing feature of IDEs
Doing it as a comment would be pretty awful. But anyway I guess the author is looking for https://lsif.dev/
-
Byfrost Indexer working with Go
If you want an example of using go compiler frontend for static analysis, checkout https://github.com/sourcegraph/lsif-go, this powers our precise code navigation indexing for Go and solves your issue of not having type information when using tree-sitter (the code is a bit hard to follow because a lot of work went into making it as fast as possible, but feel free to find your way to our Discord where we could answer questions). Dont try to reimplement type checking, its all there waiting to be used ; )
What are some alternatives?
scip - SCIP Code Intelligence Protocol
codegraph - CodeGraph - Tool that create a graph of code to show dependencies between code entities (methods, classes and etc).
difftastic - a structural diff that understands syntax 🟥🟩
codequery - A code-understanding, code-browsing or code-search tool. This is a tool to index, then query or search C, C++, Java, Python, Ruby, Go and Javascript source code. It builds upon the databases of cscope and ctags, and provides a nice GUI tool.
emerge - Emerge is a browser-based interactive codebase and dependency visualization tool for many different programming languages. It supports some basic code quality and graph metrics and provides a simple and intuitive way to explore and analyze a codebase by using graph structures.
community - Issue tracker for the community team at Sourcegraph
IDE-Block - GitHub Block providing IDE-like features to help you read code.
dark - Darklang main repo, including language, backend, and infra