Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Feature request: add GDScript (Godot) language support

Aperta
  • Qualcosa non va?
#1,618 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
godot, javascript, lua
Ambito
devtools, tooling

Direzione di ricerca

Read the Supported Languages section in README.md and the registrations in extraction/languages/index.js; compare how existing language extractors are wired. The issue leaves open whether to use a native tree-sitter grammar or extend extraction/languages/lua.js, so first determine which approach fits the project. Done means .gd files are indexed and the listed GDScript symbols can be queried.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Feature request: add GDScript (Godot) language support

Summary

GDScript — the primary scripting language for Godot Engine 4.x projects — is not currently in the list of supported languages (README.md "Supported Languages" section and extraction/languages/index.js registrations).

Why it matters

GDScript is one of the highest-popularity languages in the indie / open-source game-dev ecosystem, and Godot projects have characteristics that CodeGraph's pre-indexed model is particularly well-suited for:

  • Heavy cross-file references: Godot scenes, autoloads, and signals create a dense extends / class_name / @onready / signal graph across many .gd files. Today this requires grep + Read to reconstruct, which is exactly the workflow CodeGraph replaces.
  • Auto-sync fits the iterative gameplay-loop: CodeGraph's "index updates on every file change" model is a natural fit for the gameplay / UI iteration cycle Godot projects go through.
Concrete repro
  1. Run codegraph init in a Godot 4 project (any project with .gd files in scripts/).
  2. codegraph status reports 0 files indexed for any language matching .gd.
  3. No codegraph_explore / codegraph_query results return symbols defined in .gd files.

Expected: the 145 .gd files in a typical Godot project should appear under Files by Language, and GDScript symbols (class_name, func, signal, extends, var, @onready, preload, load) should be queryable.

Proposed approach

There are two reasonable paths; happy to send a PR either way:

A. Native tree-sitter grammar — tree-sitter-gdscript is maintained (https://github.com/PrestonKnopp/tree-sitter-gdscript) and already vendored by some tools. Mirrors how the other 27 languages in extraction/languages/ are wired.

B. Extend the existing Lua extractor — Given the recent Lua-parser work (#1616, #1617), GDScript's Lua-influenced syntax (block-by-indent, func/var declarations, extends/signal/class_name keywords layered on top) could be supported by extending extraction/languages/lua.js with a thin GDScript overlay rather than maintaining a separate extractor. Faster to land, naturally benefits from the same edge / dynamic-dispatch resolution infrastructure the Lua extractor is being improved with right now. Less accurate than a native grammar, but unblocks Godot users quickly.

Environment
  • CodeGraph v1.5.0 (/opt/homebrew/bin/codegraph via npm i -g @colbymchenry/codegraph)
  • macOS arm64
  • Test project: a Godot 4 project with ~145 .gd files and ~50 .tscn scene files

Thanks — happy to iterate on the design.

Lingua principale
C
Stelle
73.2k
Fork
4.7k
Merge medio
13h 27m
PR unite (30g)
518

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di colbymchenry/codegraph

Tutte le issue di colbymchenry/codegraph

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.