Migrate protocol_handler's custom protocol and deep-link capabilities to NativeAPI
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 35/100
- Issue 類型
- 功能
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- dart, flutter, typescript
研究方向
Start with the linked protocol_handler README and public API references to map the existing registration, launch URL, event, and listener behavior. Then inspect NativeAPI's UrlOpener and its Dart/Flutter bindings and platform integrations. Done means equivalent APIs, setup documentation and a migration example cover Android, iOS, macOS, and Windows, with the listed scenarios validated on each.
由索引模型根據 Issue 內容生成。
描述
Goal
Bring the full public capability set of protocol_handler into NativeAPI so Flutter apps can migrate without losing functionality.
Scope
Provide equivalents for:
register(String scheme)for custom protocol registration/configuration.getInitialUrl()for retrieving the URL that launched the app.onUrlReceivedfor incoming URL events.ProtocolListener.onProtocolUrlReceived(String url), listener attachment/removal, andlisteners/hasListenersinspection.
API names may change, but the migration guide should map every existing public capability to its NativeAPI equivalent.
Platform coverage
Match the source plugin's documented support: Android, iOS, macOS and Windows. Document the required Android intent filters, iOS/macOS URL scheme declarations, Windows runner integration and MSIX protocol activation configuration.
Acceptance criteria
- Expose equivalent APIs to Dart/Flutter.
- Document platform support, setup requirements and limitations.
- Provide a migration guide and example covering registration, launch URLs, incoming events and listener cleanup.
- Validate these scenarios on all four source-supported platforms.
Notes
NativeAPI's existing UrlOpener handles outbound URLs, not incoming protocol activations. The source plugin exposes no unregister API, so unregistration is not assumed to be part of migration parity. Linux support and other language bindings can be scoped separately.
References
- 主要語言
- TypeScript
- 星號
- 172
- 分支
- 16
- 平均合併
- 2 小時 11 分鐘
- 30 天內合併 PR
- 4
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
libnativeapi/nativeapi 的其他 Issue
-
難度 4/5 3-5 天 新手友好度 38/100
libnativeapi/nativeapi#30 · 2 則留言 ·
-
難度 4/5 3-5 天 新手友好度 38/100
libnativeapi/nativeapi#29 ·
-
難度 3/5 1-2 天 新手友好度 56/100
libnativeapi/nativeapi#28 · 3 則留言 ·
-
難度 4/5 3-5 天 新手友好度 48/100
libnativeapi/nativeapi#25 ·
查看 libnativeapi/nativeapi 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 62/100
-
Mend: dependency security vulnerability
難度 1/5 1-3 小時 新手友好度 65/100
fdm-monster/fdm-monster#5563 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
be-BOP-io-SA/be-BOP#2849 ·
-
難度 2/5 1-3 小時 新手友好度 79/100
維護者通常 1 天內回覆
-
1️⃣ phase/under-investigation flaky/confirmed flaky/needs-decision type/bug
難度 2/5 1-3 小時 新手友好度 65/100
growilabs/growi#12246 · 3 則留言 ·
維護者通常 1 天內回覆