Language Extensions/Plugins

[ryanhaarmann]

What is the recommended or best way to handle adding a new language but via a different package and not requiring adding it to the main source? What if I want to implement a snowflake-sql or postgres-sql language extractor, but I don't know if those belong directly in the main codebase, maybe they should be extension/integration/plugin to graphify? Additionally beyond normal languages, we have some internal overrides using jinja templates on our sql, so I want to create a language handler for this is possible, so that the "extract" is utilized and doesn't need to process through claude tokens.

[ari-lindari]

+1 to PostgreSQL support (and SQL more broadly).

This would significantly increase Graphify’s usefulness for real-world backends where business logic lives in DB functions/RPCs, not just application code.

A native extractor (e.g. via Tree-sitter SQL or similar) would allow deterministic mapping of:

• tables ↔ functions
• function ↔ function dependencies
• policies / triggers

Right now, without structured SQL extraction, a large portion of backend logic is effectively invisible to the graph.

Even a minimal first pass (DDL + function signatures + references) would be hugely valuable.

[safishamsi]

Will ship it over the weekend then! I'm also going to excel spreadsheets support