feat: add relationship tracking for GDScript - #62
Merged
Conversation
Contributor
|
✅ Quick checks success |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds full relationship tracking for GDScript, including call, signal emission, extends, and preload dependency extraction, and wires those relationships into parser and MCP integration tests.
Changes
GdscriptParserto collect call targets (includingemit_signal) and type/resource uses from extends, preload constants, and script-level loads.find_callsandfind_usesreport the expected edges.Technical Details
<script>scope to align extends/use output with other languages.Test Coverage
cargo test tests::parsers_gdscript::test_relationshipscargo test --test integration_tests test_gdscript_mcp