NativeScript / NativeScript/nativescript-cli
Open Chrome when using Chrome DevTools for debugging
還沒有人認領這個 Issue。
- 主要語言
- JavaScript
- 星號
- 1.1k
- 分支
- 204
- 平均合併
- 1 天 9 小時
- 30 天內合併 PR
- 8
描述
Currently tns debug android and tns debug ios --chrome prepare the project, run it on specified device and prints a URL which should be opened in Chrome browser.
Instead the commands should open Chrome directly and load a specified URL.
The current implementation prints the URL as it is unable to open it in Chrome. However, the changes applied in this PR allow us to generate a URL to https://chrome-devtools-frontend.appspot.com/. This URL can be safely opened in Chrome directly from CLI.
Things to consider during implementation:
- For testability, we should have an easy way to print the URL and do not open Chrome. This will be useful in CI.
- Visual Studio Code Extension does not need to open Chrome, so ensure
--no-clientoption is respected. - Chrome executable has different names on each OS. Also the
Canaryrelease has another name. Ensure the users have an easy way to set the name, specific to their system. - During debug operation, CLI LiveSyncs changes on device. This may produce different URL (the port may change), so ensure we open the URL again. In case the port is not changed, just inform the user to reconnect DevTools in the already opened tab.
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
先追蹤 tns debug android 和 tns debug ios --chrome 進入點,然後檢視 PR 3071,了解 DevTools URL 的產生方式。完成的標準是 Chrome 能開啟該 URL,CI 能在不啟動 Chrome 的情況下輸出該 URL,--no-client 仍然受到遵守,可設定可執行檔名稱,並處理 LiveSync URL 的變更。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- android, ios, javascript
- 領域
- cli, devtools, mobile-dev
- Issue 類型
- 功能
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100