Purpose of the IOSDeviceLib's interface

未关闭
#30 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
重构
描述清晰度
需要澄清
活跃度
停滞
技术栈
cpp, javascript
领域
api

调研方向

首先,将 JavaScript 接口与 mobile-cli-lib 的用法以及解析 uploadArray、downloadArray 和 postNotificationArray 的原生代码进行比较。明确 IOSDeviceLib 旨在作为代理还是面向应用的 API,然后定义所需的接口更改,以明确其用途和所接受的参数。

由索引模型根据 Issue 内容生成。

描述

If we would like to state the following:

  • "The node code is there to be able to act as a proxy between the spawned process and the rest of the code"
    If this is true.. functions like upload,download, postNotifications should not be defined in the javascript code.

  • "The node code should serve as both proxy and api to be used from applications"
    If this is true... named functions are a nice idea.
    What seems wrong is the fact that currently the only ways to find what to pass in the uploadArray, downloadArray or postNotificationArray are to take a look at the mobile-cli-lib or go to the native code to see how we are parsing the array.

It seems the purpose of IOSDeviceLib's interface is not clear enough with the current implementation.
Please correct me if I don't understand correctly.

主要语言
C++
星标
16
派生
8
平均合并
19 小时 29 分钟
30 天内合并 PR
2

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

NativeScript/ios-device-lib 的其他 Issue

查看 NativeScript/ios-device-lib 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。