React Native鸿蒙化仓库
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
chore: pr template on syncing to 77 branch Signed-off-by: linhandev <hanlin21@huawei.com> | 1 年前 | |
fix: Addressing the Issue of Vague Documentation in the AutoLink Documentation Co-authored-by: saberblack<2422489333@qq.com> # message auto-generated for no-merge-commit merge: !1883 merge master into master fix: Addressing the Issue of Vague Documentation in the AutoLink Documentation Created-by: saberblack Commit-by: saberblack Merged-by: huangyouhua Description: <!-- PLEASE REMOVE COMMENTS BEFORE MERGING TO AVOID INCLUDING THEM IN GIT HISTORY --> ## Description <!-- Briefly describe the purpose of the MR, for example: This PR mainly implements the function of remote debugging within the Metro LAN. --> Fixing the unclear description of autolink documentation, supplementing configuration information, and generating file information. ## Changes <!-- List main changes in bullet points that can be included in the changelog. Those changes should be written for application developers and react third-party library authors. Internal changes shouldn't be listed. Please start each bullet point with: - added - fixed - deprecated - removed If it is a change to add a new attribute, use [added] prefix, for example: - [added] FlatList component adds inverted attribute --> ## Test Plan <!-- How to test this PR. For example: 1. Open the Tester project 2. Execute the npm run start command ... --> Not involved ## Checklist <!-- Please conduct self inspection according to the following checklist before merging After completing the self check, fill in "x" in [], For example: - [x] Does not involve incompatible changes; if involved, has been reviewed accordingly. --> - [x] Does not involve incompatible changes; if involved, has been reviewed accordingly. - [x] Does not impact performance, or performance testing has been conducted without degradation. - [x] Complies with the relevant coding standards. - [x] Does not involve documentation updates, or the documentation has been updated. - [x] Meets testability requirements with necessary self-test cases, appropriate logging, or trace information added. - [x] No illegal file inclusions exist, such as images or code. See merge request: openharmony-sig/ohos_react_native!1883 | 10 个月前 | |
[chore]: updated to version 6.0.2.120(0.72.103) Co-authored-by: liyiqun<386941193@qq.com> # message auto-generated for no-merge-commit merge: !1852 merge master into master [chore]: updated to version 6.0.2.120(0.72.103) Created-by: liyiqn Commit-by: liyiqun Merged-by: openharmony_ci Description: <!-- 请在合并之前删除注释代码，以避免将其包含在GIT历史记录中 --> # 描述 <!-- 简要描述PR的目的，例如: 这条PR主要实现metro局域网内远程调试的功能. --> # 变更日志 <!-- 列出可包含在变更日志中的要点的主要变更。 不要列出内部更改。请以下列开头来写每个变更点： - added - fixed - deprecated - removed 如果是一条新增属性的变更，则以[added]开头，例如: - [added] FlatList组件新增inverted属性 --> # 测试步骤 <!-- 如何测试这条PR。例如： 1. 打开Tester工程. 2. 执行npm run start命令. ... --> # 合入前自检 <!-- 请在合入前根据以下条例进行自检 自检完成后在[ ]内填入"x", 例如： - [x] 不涉及非兼容性变更；若涉及，已通过相应评审。 --> - [ ] 不涉及非兼容性变更；若涉及，已通过相应评审。 - [ ] 不涉及性能或已进行性能测试且无性能劣化。 - [ ] 符合对应的编码规范。 - [ ] 不涉及文档更新，或已更新了文档。 - [ ] 针对可测试性要求，已增加必要的自测用例、合理的日志记录或Trace信息。 - [ ] 不存在非法的文件引入，包括图片和代码等 - [ ] 本PR已经在77分支开启PR或不需要在77分支合入 - 如需合入77分支，PR地址： See merge request: openharmony-sig/ohos_react_native!1852 | 10 个月前 | |
fix: Document error causing compilation failure Co-authored-by: alvancf<742997447@qq.com> # message auto-generated for no-merge-commit merge: !1866 merge master-doc1202 into master fix: Document error causing compilation failure Created-by: alvancf Commit-by: alvancf Merged-by: huangyouhua Description: <!-- Please remove all comments before submitting to avoid them being included in merge commit message --> ## Why are these changes being made? fix: Document error causing compilation failure ## Changelog <!-- List user-visible changes in a concise manner. Use one of the following verbs in past tense: - added - fixed - deprecated - removed - optimized Include [breaking] prefix for breaking changes --> ## Test Plan Compile the source code according to readme, and it can be successfully compiled without any errors ## Checklist - [x] pnpm verify command has passed successfully. - [x] No failures occurred in automatic tests on the CONCURRENT TESTER page in the tester app. - [x] No failures occurred in automatic tests on the SEQUENTIAL TESTER page in the tester app. - [x] MR does not include a breaking change or a review has been requested from a Huawei reviewer. See merge request: openharmony-sig/ohos_react_native!1866 | 10 个月前 | |
[chore]: updated to version 6.0.2.120(0.72.103) Co-authored-by: liyiqun<386941193@qq.com> # message auto-generated for no-merge-commit merge: !1852 merge master into master [chore]: updated to version 6.0.2.120(0.72.103) Created-by: liyiqn Commit-by: liyiqun Merged-by: openharmony_ci Description: <!-- 请在合并之前删除注释代码，以避免将其包含在GIT历史记录中 --> # 描述 <!-- 简要描述PR的目的，例如: 这条PR主要实现metro局域网内远程调试的功能. --> # 变更日志 <!-- 列出可包含在变更日志中的要点的主要变更。 不要列出内部更改。请以下列开头来写每个变更点： - added - fixed - deprecated - removed 如果是一条新增属性的变更，则以[added]开头，例如: - [added] FlatList组件新增inverted属性 --> # 测试步骤 <!-- 如何测试这条PR。例如： 1. 打开Tester工程. 2. 执行npm run start命令. ... --> # 合入前自检 <!-- 请在合入前根据以下条例进行自检 自检完成后在[ ]内填入"x", 例如： - [x] 不涉及非兼容性变更；若涉及，已通过相应评审。 --> - [ ] 不涉及非兼容性变更；若涉及，已通过相应评审。 - [ ] 不涉及性能或已进行性能测试且无性能劣化。 - [ ] 符合对应的编码规范。 - [ ] 不涉及文档更新，或已更新了文档。 - [ ] 针对可测试性要求，已增加必要的自测用例、合理的日志记录或Trace信息。 - [ ] 不存在非法的文件引入，包括图片和代码等 - [ ] 本PR已经在77分支开启PR或不需要在77分支合入 - 如需合入77分支，PR地址： See merge request: openharmony-sig/ohos_react_native!1852 | 10 个月前 | |
[chore]: updated to version 6.0.2.120(0.72.103) Co-authored-by: liyiqun<386941193@qq.com> # message auto-generated for no-merge-commit merge: !1852 merge master into master [chore]: updated to version 6.0.2.120(0.72.103) Created-by: liyiqn Commit-by: liyiqun Merged-by: openharmony_ci Description: <!-- 请在合并之前删除注释代码，以避免将其包含在GIT历史记录中 --> # 描述 <!-- 简要描述PR的目的，例如: 这条PR主要实现metro局域网内远程调试的功能. --> # 变更日志 <!-- 列出可包含在变更日志中的要点的主要变更。 不要列出内部更改。请以下列开头来写每个变更点： - added - fixed - deprecated - removed 如果是一条新增属性的变更，则以[added]开头，例如: - [added] FlatList组件新增inverted属性 --> # 测试步骤 <!-- 如何测试这条PR。例如： 1. 打开Tester工程. 2. 执行npm run start命令. ... --> # 合入前自检 <!-- 请在合入前根据以下条例进行自检 自检完成后在[ ]内填入"x", 例如： - [x] 不涉及非兼容性变更；若涉及，已通过相应评审。 --> - [ ] 不涉及非兼容性变更；若涉及，已通过相应评审。 - [ ] 不涉及性能或已进行性能测试且无性能劣化。 - [ ] 符合对应的编码规范。 - [ ] 不涉及文档更新，或已更新了文档。 - [ ] 针对可测试性要求，已增加必要的自测用例、合理的日志记录或Trace信息。 - [ ] 不存在非法的文件引入，包括图片和代码等 - [ ] 本PR已经在77分支开启PR或不需要在77分支合入 - 如需合入77分支，PR地址： See merge request: openharmony-sig/ohos_react_native!1852 | 10 个月前 | |
[chore]: updated to version 6.0.2.120(0.72.103) Co-authored-by: liyiqun<386941193@qq.com> # message auto-generated for no-merge-commit merge: !1852 merge master into master [chore]: updated to version 6.0.2.120(0.72.103) Created-by: liyiqn Commit-by: liyiqun Merged-by: openharmony_ci Description: <!-- 请在合并之前删除注释代码，以避免将其包含在GIT历史记录中 --> # 描述 <!-- 简要描述PR的目的，例如: 这条PR主要实现metro局域网内远程调试的功能. --> # 变更日志 <!-- 列出可包含在变更日志中的要点的主要变更。 不要列出内部更改。请以下列开头来写每个变更点： - added - fixed - deprecated - removed 如果是一条新增属性的变更，则以[added]开头，例如: - [added] FlatList组件新增inverted属性 --> # 测试步骤 <!-- 如何测试这条PR。例如： 1. 打开Tester工程. 2. 执行npm run start命令. ... --> # 合入前自检 <!-- 请在合入前根据以下条例进行自检 自检完成后在[ ]内填入"x", 例如： - [x] 不涉及非兼容性变更；若涉及，已通过相应评审。 --> - [ ] 不涉及非兼容性变更；若涉及，已通过相应评审。 - [ ] 不涉及性能或已进行性能测试且无性能劣化。 - [ ] 符合对应的编码规范。 - [ ] 不涉及文档更新，或已更新了文档。 - [ ] 针对可测试性要求，已增加必要的自测用例、合理的日志记录或Trace信息。 - [ ] 不存在非法的文件引入，包括图片和代码等 - [ ] 本PR已经在77分支开启PR或不需要在77分支合入 - 如需合入77分支，PR地址： See merge request: openharmony-sig/ohos_react_native!1852 | 10 个月前 | |
fix: include attachments in nested text touch targets Attachments were excluded from touch target list and fragment rects calculation, creating unresponsive areas. Now all fragments (text and attachments) are included. Signed-off-by: Patryk Fryda <patryk.fryda@swmansion.com> | 10 个月前 | |
feat: ArkTSMessageHandler; fix: npm run format:cpp Signed-off-by: hyh <huangyouhua2@huawei.com> | 2 年前 | |
chore: setup CPP linter ## Summary Signed-off-by: hyh <huangyouhua2@huawei.com> | 2 年前 | |
!431 feat: Add a new internal HVigor plugin for compiling release and bytecode HAR packages. Merge pull request !431 from xiedairong/hvigor Revert commit: !431 feat: Add a new internal HVigor plugin for compiling release and bytecode HAR packages. This revert commit: 70b12671517db680f9bfe5d1c14c6932a428b2c5 Signed-off-by: 谢代荣 <xiedairong@huawei.com> | 1 年前 | |
Revert "门禁测试" This reverts commit 4b7cbd96fd83c763035c70b363ea2aec406ffadb. | 1 年前 | |
fix: fix a crash caused by removing a NAPI reference on JS thread Co-authored-by: gyange<gyange@163.com> # message auto-generated for no-merge-commit merge: !1801 merge master into master fix: fix a crash caused by removing a NAPI reference on JS thread Created-by: gyange Commit-by: gyange Merged-by: huangyouhua Description: <!-- 请在合并之前删除注释代码，以避免将其包含在GIT历史记录中 --> # 描述 <!-- fix a crash caused by removing a NAPI reference on JS thread. --> # 变更日志 <!-- 列出可包含在变更日志中的要点的主要变更。 不要列出内部更改。请以下列开头来写每个变更点： - added - fixed - deprecated - removed 如果是一条新增属性的变更，则以[added]开头，例如: - [added] FlatList组件新增inverted属性 --> # 测试步骤 <!-- 如何测试这条PR。例如： 1. 打开Tester工程. 2. 执行npm run start命令. ... --> # 合入前自检 <!-- 请在合入前根据以下条例进行自检 自检完成后在[ ]内填入"x", 例如： - [x] 不涉及非兼容性变更；若涉及，已通过相应评审。 --> - [ ] 不涉及非兼容性变更；若涉及，已通过相应评审。 - [x] 不涉及性能或已进行性能测试且无性能劣化。 - [ ] 符合对应的编码规范。 - [ ] 不涉及文档更新，或已更新了文档。 - [ ] 针对可测试性要求，已增加必要的自测用例、合理的日志记录或Trace信息。 - [ ] 不存在非法的文件引入，包括图片和代码等 - [ ] 本PR已经在77分支开启PR或不需要在77分支合入 - 如需合入77分支，PR地址： See merge request: openharmony-sig/ohos_react_native!1801 | 11 个月前 | |
[chore]: updated to version 6.0.2.120(0.72.103) Co-authored-by: liyiqun<386941193@qq.com> # message auto-generated for no-merge-commit merge: !1852 merge master into master [chore]: updated to version 6.0.2.120(0.72.103) Created-by: liyiqn Commit-by: liyiqun Merged-by: openharmony_ci Description: <!-- 请在合并之前删除注释代码，以避免将其包含在GIT历史记录中 --> # 描述 <!-- 简要描述PR的目的，例如: 这条PR主要实现metro局域网内远程调试的功能. --> # 变更日志 <!-- 列出可包含在变更日志中的要点的主要变更。 不要列出内部更改。请以下列开头来写每个变更点： - added - fixed - deprecated - removed 如果是一条新增属性的变更，则以[added]开头，例如: - [added] FlatList组件新增inverted属性 --> # 测试步骤 <!-- 如何测试这条PR。例如： 1. 打开Tester工程. 2. 执行npm run start命令. ... --> # 合入前自检 <!-- 请在合入前根据以下条例进行自检 自检完成后在[ ]内填入"x", 例如： - [x] 不涉及非兼容性变更；若涉及，已通过相应评审。 --> - [ ] 不涉及非兼容性变更；若涉及，已通过相应评审。 - [ ] 不涉及性能或已进行性能测试且无性能劣化。 - [ ] 符合对应的编码规范。 - [ ] 不涉及文档更新，或已更新了文档。 - [ ] 针对可测试性要求，已增加必要的自测用例、合理的日志记录或Trace信息。 - [ ] 不存在非法的文件引入，包括图片和代码等 - [ ] 本PR已经在77分支开启PR或不需要在77分支合入 - 如需合入77分支，PR地址： See merge request: openharmony-sig/ohos_react_native!1852 | 10 个月前 | |
更新Committers列表 Signed-off-by: x30015140 <xiedairong@huawei.com> | 1 年前 | |
LICENSE文件更新，新增LICENSE-MIT Signed-off-by: Dark <3166955090@qq.com> | 1 年前 | |
LICENSE文件更新，新增LICENSE-MIT Signed-off-by: Dark <3166955090@qq.com> | 1 年前 | |
fix: initial screen size for Modal Co-authored-by: Arkadiusz Kasprzyk<arkadiusz.kasprzyk@swmansion.com> # message auto-generated for no-merge-commit merge: !1823 merge kas/modal-initial-size into master fix: initial screen size for Modal Created-by: arkadiuszkasprzyk Commit-by: Arkadiusz Kasprzyk Merged-by: huangyouhua Description: ## Description Currently, Modal sometimes isn't displayed if screenSize is 0. / only show modal after the screen size has been set and processed by RN auto isScreenSizeSet = m_state && m_state->getData().screenSize.height != 0 && m_state->getData().screenSize.width != 0; auto shouldShowDialog = !m_dialogHandler.isShow() && isScreenSizeSet; This MR sets initial screenSize by adpoting approach used on the 77 branch: https://gitcode.com/openharmony-sig/ohos_react_native/pull/1184. ## Changes - fixed modal not being displayed in certain scenarios ## Test Plan 1. Create your own ecosystem tester 72 project with linked reanimated. 2. Run the demo below and notice modal isn't displayed. 3. Patch ReactCommon/react/renderer/components/modal/ModalHostViewState.h by assigning some reasonable screen size to screenSize 4. Run the demo again and notice modal is displayed. 5. In this tester project add log screen size in createInitialState tester/harmony/react_native_openharmony/src/main/cpp/RNOHCorePackage/ComponentDescriptors/ModalHostViewComponentDescriptor.cpp 6. Run some Modal test. 7. Notice non-zero screenSize is logged and there are no regressions. ## Checklist - [x] Does not involve incompatible changes; if involved, has been reviewed accordingly. - [x] Does not impact performance, or performance testing has been conducted without degradation. - [x] Complies with the relevant coding standards. - [x] Does not involve documentation updates, or the documentation has been updated. - [ ] Meets testability requirements with necessary self-test cases, appropriate logging, or trace information added. - [x] No illegal file inclusions exist, such as images or code. See merge request: openharmony-sig/ohos_react_native!1823 | 10 个月前 | |
update README.OpenSource Signed-off-by: Galen wei <1947612015@qq.com> | 1 年前 | |
fix: Document error causing compilation failure Co-authored-by: alvancf<742997447@qq.com> # message auto-generated for no-merge-commit merge: !1866 merge master-doc1202 into master fix: Document error causing compilation failure Created-by: alvancf Commit-by: alvancf Merged-by: huangyouhua Description: <!-- Please remove all comments before submitting to avoid them being included in merge commit message --> ## Why are these changes being made? fix: Document error causing compilation failure ## Changelog <!-- List user-visible changes in a concise manner. Use one of the following verbs in past tense: - added - fixed - deprecated - removed - optimized Include [breaking] prefix for breaking changes --> ## Test Plan Compile the source code according to readme, and it can be successfully compiled without any errors ## Checklist - [x] pnpm verify command has passed successfully. - [x] No failures occurred in automatic tests on the CONCURRENT TESTER page in the tester app. - [x] No failures occurred in automatic tests on the SEQUENTIAL TESTER page in the tester app. - [x] MR does not include a breaking change or a review has been requested from a Huawei reviewer. See merge request: openharmony-sig/ohos_react_native!1866 | 10 个月前 | |
fix: Document error causing compilation failure Co-authored-by: alvancf<742997447@qq.com> # message auto-generated for no-merge-commit merge: !1866 merge master-doc1202 into master fix: Document error causing compilation failure Created-by: alvancf Commit-by: alvancf Merged-by: huangyouhua Description: <!-- Please remove all comments before submitting to avoid them being included in merge commit message --> ## Why are these changes being made? fix: Document error causing compilation failure ## Changelog <!-- List user-visible changes in a concise manner. Use one of the following verbs in past tense: - added - fixed - deprecated - removed - optimized Include [breaking] prefix for breaking changes --> ## Test Plan Compile the source code according to readme, and it can be successfully compiled without any errors ## Checklist - [x] pnpm verify command has passed successfully. - [x] No failures occurred in automatic tests on the CONCURRENT TESTER page in the tester app. - [x] No failures occurred in automatic tests on the SEQUENTIAL TESTER page in the tester app. - [x] MR does not include a breaking change or a review has been requested from a Huawei reviewer. See merge request: openharmony-sig/ohos_react_native!1866 | 10 个月前 | |
新增构建文档 Signed-off-by: x30015140 <xiedairong@huawei.com> | 1 年前 |
React Native for OpenHarmony (RNOH)
欢迎阅读React Native for OpenHarmony文档，参与React Native for OpenHarmony开发者文档开源项目，与我们一起完善开发者文档。
RNOH版本演进规划和分支策略
您可以在RNOH版本演进规划和分支策略中了解更多关于我们对React Native的OpenHarmony适配版本的说明。
启动
前提条件
安装了HarmonyOS NEXT的模拟器或真机
该项目需要HarmonyOS NEXT上进行测试。
华为开发者账号
运行应用程序时，需要用到华为开发者账号进行签名。
DevEco Studio
从官网下载并安装最新版本 DevEco Studio。
启动项目
如果是编译源码，在拉取工程后需要在工程的根目录执行
git submodule update --init --recursive命令，拉取三方库依赖。
- 打开终端（命令行工具）并导航到react-native-harmony-cli目录，然后执行
npm i && npm pack。 - 在终端中导航到react-native-harmony目录，然后执行
npm i && npm pack。 - 在终端中导航到react-native-harmony-sample-package目录，然后执行
npm i && npm pack。 - 导航到tester目录，然后执行
npm run i（不是 npm i）。 - 在tester目录中运行
npm start以启动Metro服务器。 - 设置
RNOH_C_API_ARCH环境变量的值为1，具体参考配置CAPI版本环境变量。 - 在DevEco Studio中打开
tester/harmony项目并等待后台同步完成。 - 连接设备。
- 点击 File > Project Structure > Signing Configs，登录并完成签名。
- 选择
entry（右上角）。 - 点击【Run 'entry'】按钮（右上角）运行项目。
说明： 该tester项目工程主要用于开发自测试各种用例场景，如果在运行tester中的用例时遇到问题，通过提issues来咨询。
使用说明
- React Native的使用问题可查阅React Native 官网或React Native 中文网。
- RNOH的使用问题可查阅中文文档或英文文档。