| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
feat: 72 supports the command npx @react-native-oh/react-native-harmony-cli init. Co-authored-by: quguiren<quguiren1@huawei-partners.com> # message auto-generated for no-merge-commit merge: merge rnoh_cli_72 into master feat: 72 supports the command npx @react-native-oh/react-native-harmony-cli init. Created-by: quguiren Commit-by: quguiren Merged-by: huangyouhua Description: ## Description This PR implements the ability to create a new RNOH project using npx @react-native-oh/react-native-harmony-cli init project. ## Changes - [added] Added initialization feature to @react-native-oh/react-native-harmony-cli - [added] Added --simulator parameter to the run-harmony command to specify the HarmonyOS simulator. ## Test Plan 1. Create a new project using npx @react-native-oh/react-native-harmony-cli init project1 2. Start the HarmonyOS simulator or connect a Harmony phone 3. Open the created project with DevEco Studio, synchronize, and sign it 4. Run npx react-native run-harmony to build and run the project 5. Run npx react-native start to start Metro and check if hot reloading works properly * Test results: The project can be created successfully The app runs normally ## 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. - [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!1292 | 1 年前 | |
feat: Add a new --ets-output-path parameter to codegen-harmony. Co-authored-by: 谢代荣<xiedairong@huawei.com> # message auto-generated for no-merge-commit merge: merge master-codegen into master feat: Add a new --ets-output-path parameter to codegen-harmony. Created-by: xiedrsz Commit-by: 谢代荣 Merged-by: huangyouhua Description: ## Description The bytecode har package does not allow generating codegen's ets code within oh_modules. Therefore, it is necessary to add a --ets-output-path parameter to the codegen-harmony command to generate ets files in other locations. ## Changes - added a new --ets-output-path parameter to codegen-harmony. ## Test Plan 1. Open the Tester project. 1. Reinstall the dependencies. 1. Run the command npm start. 1. Check if ets code has been generated in the harmony/react_native_openharmony/generated directory and whether '../../ts' has been changed to '@rnoh/react-native-openharmony/ts'. ## 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. - [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!1539 | 1 年前 | |
Fix: The event is triggered multiple times when custom ArkTS components share the same event name across multiple packages. Co-authored-by: 谢代荣<xiedairong@huawei.com> # message auto-generated for no-merge-commit merge: merge master-codegen into master Fix: The event is triggered multiple times when custom ArkTS components share the same event name across multiple packages. Created-by: xiedrsz Commit-by: 谢代荣 Merged-by: huangyouhua Description: ## Description Fix: The event is triggered multiple times when custom ArkTS components share the same event name across multiple packages. ## Changes - [added] Add a property componentName to ShadowViewEntry. - [fixed] When receiving an event, verify whether the component to which the event belongs originates from the current package. ## Test Plan 1. Reinstall Dependencies for the Tester Project. 1. Open the Tester. 1. Check CustomNativeComponentTest. ## 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. - [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!1493 | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 |