Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

feat(bridge): Kotlin Multiplatform channel — Kotlin → generated ObjC framework → Swift edges

オープン
  • 何か問題がありますか？
#1,676 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
静か
技術スタック
kotlin, objective-c, swift
領域
devtools

調査の方向性

Start by reading the README section “Mixed iOS / React Native / Expo bridging” and the existing bridge-channel implementations that synthesize heuristic edges. Trace how those channels derive names, attach provenance and metadata, and match ObjC to Swift. Done means common Kotlin/Native exports can connect Kotlin symbols through derived ObjC selectors to Swift consumers, while unsupported or hidden constructs do not produce candidates.

索引モデルが issue の本文から書いたものです。

説明

Summary

The cross-language bridging layer (README → "Mixed iOS / React Native / Expo bridging") covers Swift↔ObjC auto-bridging, the React Native legacy bridge, TurboModules, RN event channels, Expo Modules, and Fabric/Paper views — but not Kotlin Multiplatform: the Kotlin → generated ObjC framework → Swift seam that every KMP mobile monorepo lives on. On such a repo, a shared Kotlin symbol's callers/impact never include its Swift consumers, so blast-radius answers on exactly the symbols both platforms depend on are silently incomplete.

Repo shape

A typical KMP monorepo: shared/src/commonMain/kotlin/** compiled into an Apple framework (via the Kotlin/Native ObjC export), consumed from iosApp/**/*.swift as import SharedKit. Both sides are already indexed individually — Kotlin edges resolve well, Swift symbols/files resolve — but no edge crosses the boundary in either direction.

Why this looks feasible in the existing architecture

The bridge channels already synthesize edges from mechanical naming rules and tag them provenance:'heuristic' with metadata.synthesizedBy. Kotlin/Native's ObjC export rules are similarly mechanical, and the Swift→ObjC prepositional rules you already implement do half the work once the Kotlin→ObjC name is derived:

  • Class/interface/object names surface with the framework or @ObjC* name; top-level functions attach to a <FileName>Kt facade class.
  • @ObjcName / @ObjCName and @HidesFromObjC annotations override or remove exposure — parseable from the Kotlin source, same as you verify @objc exposure on the Swift↔ObjC channel.
  • suspend fun foo(bar: T) exports as a completionHandler: method — a deterministic transform of the Kotlin signature.
  • Interop-invisible constructs (sealed hierarchy details, default args expanding to overload sets) can simply not emit candidates — a bridge that only claims the mechanical subset is still a large win over no edges.

A kmp-objc-bridge channel emitting the Kotlin-symbol → derived-ObjC-selector candidates, then reusing the existing ObjC→Swift reverse-bridge matching, would connect the seam for the common cases.

Impact / motivation

The failure mode is the dangerous kind: an agent asked "is this shared Kotlin symbol safe to delete" gets a confident, wrong "no callers" because the only callers are Swift (we have hit exactly this, via a renamed Swift binding, before adopting codegraph). We currently mitigate procedurally (repo guidance: treat the KMP boundary as invisible; cross-language name search before any unused/impact conclusion), but the graph is the right place for these edges, and issue #765's point about explore/edge reliability on multi-language repos applies doubly when a whole language boundary has no channel.

Happy to test a build against a real ~2,200-file KMP monorepo (Kotlin + Swift + generated framework) and report resolution rates if that helps.

主要言語
C
スター
73.2k
フォーク
4.7k
平均マージ
13時間 27分
マージ済み PR（30日）
518

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

colbymchenry/codegraph のほかの issue

colbymchenry/codegraph の issue をすべて見る

似ている issue

C の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。