feat(resolution): mixed iOS / React Native / Expo cross-language bridging (#430)
Implements the design from `docs/design/mixed-ios-and-react-native-bridging.md`.
Closes the cross-language flow gap so `trace` / `callers` / `callees` / `impact` connect end-to-end across language boundaries in real iOS, React Native, and Expo codebases.
## Bridges shipped
| Boundary | Mechanism | Real-codebase validation |
|---|---|---|
| **Swift ↔ Objective-C** | Resolver applying Apple's @objc auto-bridging name math + Cocoa preposition prefixes | Charts (S, 269) · realm-swift (M, 369) · wikipedia-ios (L, 1734) |
| **React Native legacy bridge** | Resolver parsing `RCT_EXPORT_MODULE` / `RCT_EXPORT_METHOD` / `RCT_REMAP_METHOD` (ObjC) + `@ReactMethod` (Java/Kotlin) | AsyncStorage (S, ~60) · react-native-svg (M, ~700) · react-native-firebase (L, ~1100) |
| **React Native TurboModules** | Resolver treating `Native<X>.ts` spec interface as ground truth | via RNSvg + RNFirebase subsets |
| **Native → JS events** | Synthesizer matching native `sendEventWithName:`/`emit(...)` to JS `addListener('e', handler)` keyed by literal event name; falls back to enclosing constant/variable for wrapper-API parameter handlers | RNGeolocation (S) · RNFirebase (L) |
| **Expo Modules** | Framework extract synthesizes `method` nodes from Swift/Kotlin `Module { Name("X"); Function("y") { ... } }` DSL | expo-haptics (S, 14) · expo-camera (M, 72) · ExpoSweep (L, 332, 7 packages) |
| **Fabric + legacy Paper view components** | Extract `component` + `property` nodes from Codegen `codegenNativeComponent<Props>('Name', ...)` specs AND legacy `RCT_EXPORT_VIEW_PROPERTY` / `@ReactProp` macros, then synthesize component → native class by name+suffix convention | react-native-segmented-control (S, legacy) · react-native-screens (M, Codegen) · react-native-skia (L, hybrid monorepo) |
## Bug fixes surfaced along the way
- `tree-sitter.ts` message_expression — multi-keyword ObjC call sites now reconstruct `a🅱️` selectors so they resolve to multi-part method definitions (gap discovered post-#165; 0 → 84 call edges to `GET:parameters:...` style methods on AFNetworking).
- `src/index.ts` resolver lifecycle — `indexAll()` now re-initializes the resolver after extraction so framework `detect()` sees the populated index. Pre-existing latent bug that affected UIKit and SwiftUI resolvers too.
- `src/extraction/index.ts` `buildDetectionContext` — added `listDirectories` so framework detect() can probe monorepo subpackages uniformly (fix needed for react-native-skia detection).
## Regression check on 5 control repos
| Repo | Result |
|---|---|
| Express (small JS) | ✅ unchanged — 266 routes, express framework detected |
| Excalidraw (medium TS/React) | ✅ 9284 nodes (CLAUDE.md baseline ~9290); canonical `trace(mutateElement, renderStaticScene)` returns the flow |
| Django realworld (Python) | ✅ django framework detected, 16 routes |
| Spring petclinic (Java) | ✅ spring framework detected, 17 routes |
| Texture (pure ObjC, large) | ✅ exactly matches #165 baseline: 4702 methods, 894 classes, 808/808 file coverage, 913 multi-keyword selectors, 55 protocols, 1036 properties |
## Tests
928 passing (+87 net new bridge tests across the 5 channels); 2 pre-existing skips. The mcp-staleness-banner / watcher parallel flakiness is unchanged by this work (different test fails each run, all pass in isolation; pre-existing on main).
## Documentation
- README: new 'Mixed iOS / React Native / Expo bridging' section with the per-boundary table and validation-corpus links.
- CHANGELOG `[Unreleased]`: full entry per bridge with measurements.
- `docs/design/mixed-ios-and-react-native-bridging.md`: the design doc (§8 measurements filled in across §8a-§8g).
- `docs/design/dynamic-dispatch-coverage-playbook.md` §6 coverage matrix: six new rows.
- `.claude/skills/agent-eval/corpus.json`: four new sections covering 15 real GitHub repos for the eval harness.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
This commit is contained in:
@@ -555,6 +555,24 @@ export class ExtractionOrchestrator {
|
||||
return null;
|
||||
}
|
||||
},
|
||||
// Monorepo support — needed by framework detect()s that probe
|
||||
// subpackage manifests (e.g. fabric-view looking at
|
||||
// packages/<sub>/package.json when the root manifest is just a
|
||||
// workspace declaration). Matches the resolver-context shape.
|
||||
listDirectories: (relativePath: string) => {
|
||||
const target =
|
||||
relativePath === '.' || relativePath === ''
|
||||
? rootDir
|
||||
: path.join(rootDir, relativePath);
|
||||
try {
|
||||
return fs
|
||||
.readdirSync(target, { withFileTypes: true })
|
||||
.filter((entry) => entry.isDirectory())
|
||||
.map((entry) => entry.name);
|
||||
} catch {
|
||||
return [];
|
||||
}
|
||||
},
|
||||
};
|
||||
}
|
||||
|
||||
|
||||
@@ -1467,9 +1467,26 @@ export class TreeSitterExtractor {
|
||||
}
|
||||
}
|
||||
} else if (node.type === 'message_expression') {
|
||||
const methodField = getChildByField(node, 'method');
|
||||
if (methodField) {
|
||||
const methodName = getNodeText(methodField, this.source);
|
||||
// ObjC message expressions emit one `method` field child per selector
|
||||
// keyword: `[obj a:1 b:2 c:3]` has three `method=identifier` siblings.
|
||||
// Joining them with `:` reconstructs the full selector and matches the
|
||||
// multi-part selector names produced by the ObjC method_definition
|
||||
// extractor (`extractObjcMethodName` in languages/objc.ts). Without this
|
||||
// join, multi-keyword call sites only emitted the first keyword and never
|
||||
// resolved to their target methods (e.g. `GET:parameters:headers:...` had
|
||||
// zero callers despite obviously being called).
|
||||
const methodKeywords: string[] = [];
|
||||
for (let i = 0; i < node.namedChildCount; i++) {
|
||||
if (node.fieldNameForNamedChild(i) === 'method') {
|
||||
const kw = node.namedChild(i);
|
||||
if (kw) methodKeywords.push(getNodeText(kw, this.source));
|
||||
}
|
||||
}
|
||||
if (methodKeywords.length > 0) {
|
||||
const methodName: string =
|
||||
methodKeywords.length === 1
|
||||
? (methodKeywords[0] as string)
|
||||
: methodKeywords.map((k) => `${k}:`).join('');
|
||||
const receiverField = getChildByField(node, 'receiver');
|
||||
const SKIP_RECEIVERS = new Set(['self', 'super']);
|
||||
if (receiverField && receiverField.type !== 'message_expression') {
|
||||
|
||||
Reference in New Issue
Block a user