Is your feature request related to a problem? Please describe.
I am working on a mixed Python and MATLAB codebase (toolchain) on a highly secure company laptop. Because of corporate restrictions, I cannot use external LLM API keys, so I rely exclusively on the --code-only flag to generate the knowledge graph locally.
While my Python files are parsed perfectly, all my MATLAB (.m) files are skipped because Graphify currently lacks a Tree-sitter grammar/AST extractor for them.
Here is the warning I get during extraction:
warning: 272 file(s) are classified as code but graphify has no AST extractor for their language, so they contributed nothing to the graph: .m (272). Please open an issue to request support for these (#1689).
Describe the solution you'd like
Please add native local AST parsing support for MATLAB (.m) files using a tree-sitter grammar (e.g., tree-sitter-matlab). This would allow the files to be included in the graph.json and GRAPH_REPORT.md without requiring an API key.
Describe alternatives you've considered
Currently, I have to manually use the "MATLAB Dependency Analyzer" from the MATLAB IDE, export the architecture as a CSV, and feed it manually to GitHub Copilot via a custom .github/matlab_dependencies.md file alongside Graphify's Python report. Having everything unified in Graphify would be a huge time-saver.
Additional context
MATLAB is heavily used in automotive, aerospace, and engineering toolchains alongside Python. Supporting it locally would be a great addition for enterprise users working in restricted environments.
Is your feature request related to a problem? Please describe.
I am working on a mixed Python and MATLAB codebase (toolchain) on a highly secure company laptop. Because of corporate restrictions, I cannot use external LLM API keys, so I rely exclusively on the
--code-onlyflag to generate the knowledge graph locally.While my Python files are parsed perfectly, all my MATLAB (
.m) files are skipped because Graphify currently lacks a Tree-sitter grammar/AST extractor for them.Here is the warning I get during extraction:
Describe the solution you'd like
Please add native local AST parsing support for MATLAB (
.m) files using a tree-sitter grammar (e.g.,tree-sitter-matlab). This would allow the files to be included in thegraph.jsonandGRAPH_REPORT.mdwithout requiring an API key.Describe alternatives you've considered
Currently, I have to manually use the "MATLAB Dependency Analyzer" from the MATLAB IDE, export the architecture as a CSV, and feed it manually to GitHub Copilot via a custom
.github/matlab_dependencies.mdfile alongside Graphify's Python report. Having everything unified in Graphify would be a huge time-saver.Additional context
MATLAB is heavily used in automotive, aerospace, and engineering toolchains alongside Python. Supporting it locally would be a great addition for enterprise users working in restricted environments.