Dart Support in Maguyva: Code Graphs for Flutter and Dart Apps

Where Dart trips up shallow AI tools

Dart spreads one type across several constructs. A class can extend one base, implement several interfaces, and mix in behaviour with mixins. Extension methods attach members to types defined elsewhere, and named and factory constructors hide which class actually gets built. Text search finds the names but not the structure behind them.

Maguyva gives an agent that structure, so it can follow a change from a widget to the service it depends on.

What Maguyva extracts in Dart

Maguyva covers .dart files. Classes, mixins, and extensions are extracted as types. The functions preset in structural_search covers functions, methods, local functions, lambdas, and generative, const, and factory constructors. Signatures record optional positional and named parameter groups and static members, and definition names drop trailing ? and !.

Imports normalise import, part, and library directives and drop their show, hide, and as clauses. A call through an import prefix, such as http.get after import 'package:http/http.dart' as http, stays in the graph.

Receiver typing follows parameters, typed and initialised variables, getters, and for-in loops over lists, sets, and iterables, and treats var and dynamic as inferred. extends, implements, and with clauses are followed when resolving inherited members. The graph also records instantiation, type references, reads and writes, and exception edges.

Example agent prompts

• “Who calls CartRepository.addItem, and from which widgets?” (find_symbol, then dependency_search incoming)
• “Which classes implement PaymentGateway?” (dependency_search)
• “Trace how the checkout button reaches the payments API.” (get_task_context)

Known limits

• About 200 Dart core-library names are filtered from relationships, including collection helpers such as map, where, and forEach, Future and Stream methods such as then and listen, and the dart: libraries. Use text_pattern_search for them.
• Dart signature nodes keep the body as a sibling, so in structural_search results a local function or lambda can overlap the callable that contains it, and getters and setters appear as method signatures.

Next steps

Connect a repository with the quickstart, then check the support matrix on the compatibility page. For other mobile codebases, read the Kotlin guide and the Swift guide.