Module language_capabilities 

Structs

LanguageCapabilities

LanguageCapabilityRow

Per-language capability row for a project: which analyses are available for a language and how many files use it. Backs the dashboard capability legend so each detected language is labelled honestly (symbols / import edges / calls).

Enums

LanguageId

Constants

ALL_LANGUAGES

Every language the property graph / code-map can index, for capability enumeration and UI hints. Keep in sync with language_for_ext.

Functions

callgraph_supported_language_names

Friendly names of every language with call-graph extraction support.

capabilities

graph_supported_language_names

Friendly names of every graph-indexable language (e.g. for an empty-graph hint).

is_indexable_ext

language_capability_matrix

Build a capability matrix for the languages actually present in file_paths, sorted by file count (desc) then name. symbols/imports come from capabilities(); call_graph from supports_call_graph().

language_capability_matrix_realized

Like language_capability_matrix but enriched with realized counts for this project: how many symbols, import edges and (optionally) call edges were actually produced per language — not merely whether the language could produce them. This turns an honest “imports ✓” into “imports ✓ (142)” / “✓ (0 found)”, so an empty graph view explains itself.

language_for_ext

language_for_path

scan_unsupported_source_languages

Bounded project scan returning programming languages present in root that lean-ctx does not graph-index, with file counts (descending, capped to 5). Honors .gitignore/hidden like the graph walker and stops after max_entries filesystem entries. Lets the dashboard turn a confusing empty graph into a clear “Lua is not graph-indexed” message instead of an endless loading state.

supports_call_graph

Whether lean-ctx extracts call sites for a language (i.e. it can populate the call graph). Keep in sync with deep_queries::calls::parse_call — a language missing there yields zero call edges, which the dashboard must communicate honestly instead of suggesting an index rebuild that cannot help.