NativeScript / NativeScript/nativescript-cli
Allow the use of native ios and android framework's solutions/projects rather than an pre-build .framework/.aar file
還沒有人認領這個 Issue。
- 主要語言
- JavaScript
- 星號
- 1.1k
- 分支
- 204
- 平均合併
- 1 天 9 小時
- 30 天內合併 PR
- 8
描述
Is your feature request related to a problem? Please describe.
At the moment as a plugin developer I have to pre-build my native framework I have from iOS into an embedded .framework file and for Android into an .aar file and place those into the platforms directory of my plugin. I would like to be able to tell the NativeScript CLI where the actual Xcode/Android Studio projects if my plugin are located and have the CLI use them as "referenced projects" for the output that it created in the platforms folder of the {N} application. The idea is to be able to open that output into Xcode/Android Studio and if that output from the CLI is using a referenced of my native framework's solutions they will be included as "side" projects and I will be able to change my native code and use the IDE rebuild and start functionality (like a native iOS and Android development workflow)
Describe the solution you'd like
Currently the CLI creates the output in the the "platforms" directory (after tns build ios/android command) in such a way that it simply uses the pre-build .framework/.aar files from each node_modules {N} plugin into the build Xcode/Android Studio project of the {N} app. If the CLI can instruct the runtime to not simply use and look for .framework/.aar files but instead use an actual Xcode/Android Studio solution which builds those .framework/.aar files it will be possible to implement an functionality into the iOS and Android runtimes that will use those projects.
Describe alternatives you've considered
Currently the only way to streamline the development workflow of a plugin developer who creates a native iOS/Android library is to either:
- Build and manually move the product of the library to the "platforms" directory of his plugin
or - Use the newly created "nativescript-dev-debugging" plugin which provides workflows for such actions
The drawbacks from both approaches is that they require a full build if the {N} app after the library is replaced (--syncAllFiles).
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
先追蹤 tns build ios/android 如何在 platforms 目錄中建立應用程式輸出,以及目前如何使用外掛程式的 .framework 和 .aar 檔案。將該工作流程與 nativescript-dev-debugging 比較;完成的標準是,可以參照外掛程式提供的 Xcode 和 Android Studio 專案,將其作為附屬專案納入,並透過原生 IDE 工作流程重新建置。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- android, ios, javascript
- 領域
- cli, mobile
- Issue 類型
- 功能
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100