From 0e5b0f8137fe0db638b7fa8693aa300ebb2f9ba3 Mon Sep 17 00:00:00 2001 From: Gloria Date: Fri, 17 Mar 2023 16:27:28 +0800 Subject: [PATCH] Deleted no-check from docs Signed-off-by: wusongqing --- .../fa-model-development-overview.md | 3 +- .../application-models/module-switch.md | 12 +++--- .../application-models/thread-model-fa.md | 4 +- .../uiability-intra-device-interaction.md | 2 +- .../uiability-launch-type.md | 2 +- .../windowextensionability.md | 40 +++++++++---------- en/application-dev/faqs/faqs-ability.md | 2 +- en/application-dev/faqs/faqs-language.md | 2 +- .../napi/neural-network-runtime-guidelines.md | 2 +- .../reference/apis/js-apis-nfcTag.md | 2 +- .../reference/apis/js-apis-url.md | 2 +- .../reference/apis/js-apis-worker.md | 2 +- .../ts-container-ability-component.md | 2 +- .../porting/porting-thirdparty-cmake.md | 2 +- .../porting/porting-thirdparty-makefile.md | 2 +- .../subsystems/subsys-dfx-overview.md | 1 - en/release-notes/OpenHarmony-v3.2-beta5.md | 2 +- .../v3.2-beta3/changelog-v3.2-beta3.md | 1 - 18 files changed, 40 insertions(+), 45 deletions(-) diff --git a/en/application-dev/application-models/fa-model-development-overview.md b/en/application-dev/application-models/fa-model-development-overview.md index b717de9153..f26280e2cc 100644 --- a/en/application-dev/application-models/fa-model-development-overview.md +++ b/en/application-dev/application-models/fa-model-development-overview.md @@ -3,8 +3,7 @@ During application development based on the Feature Ability (FA) model, the following tasks are involved in the application model. - - **Table 1** FA model development process +**Table 1** FA model development process | Task| Introduction| Guide| | -------- | -------- | -------- | diff --git a/en/application-dev/application-models/module-switch.md b/en/application-dev/application-models/module-switch.md index a6e532e948..b248958fc0 100644 --- a/en/application-dev/application-models/module-switch.md +++ b/en/application-dev/application-models/module-switch.md @@ -3,7 +3,7 @@ When switching an application from the FA model to the stage model, you must migrate the configurations under the **module** tag in the **config.json** file to the **module** tag in the **module.json5** file. -### **Table 1** module comparison +**Table 1** module comparison | Field Name in the FA Model| Field Description| Field Name in the Stage Model| Difference| | -------- | -------- | -------- | -------- | @@ -26,8 +26,7 @@ When switching an application from the FA model to the stage model, you must mig | commonEvents | Common events.| common_event_config.json| In the stage model, the **common_event_config.json** file is defined in **resources/base/profile** in the development view.| | entryTheme | Keyword of an OpenHarmony internal theme.| / | This configuration is not supported in the stage model.| - -### Table 2 metaData comparison +**Table 2** metaData comparison | Field Name Under metaData in the FA Model| Field Description| Field Name Under metaData in the Stage Model| Difference| | -------- | -------- | -------- | -------- | @@ -35,7 +34,7 @@ When switching an application from the FA model to the stage model, you must mig | results | Metadata of the ability return value.| / | This configuration is not supported in the stage model.| | customizeData | Custom metadata of the parent component. **parameters** and **results** cannot be configured in **application**.| metadata | See [Table 3](#table-3-comparison-between-customizedata-under-metadata-in-the-fa-model-and-metadata-in-the-stage-model).| -### Table 3 Comparison between customizeData under metaData in the FA model and metadata in the stage model +**Table 3** Comparison between customizeData under metaData in the FA model and metadata in the stage model | Field Name Under customizeData in metaData in the FA Model| Field Description| Field Name Under metaData in the Stage Model| Difference| | -------- | -------- | -------- | -------- | @@ -43,15 +42,14 @@ When switching an application from the FA model to the stage model, you must mig | value | Value of the data item. The value is a string with a maximum of 255 bytes.| value | None.| | extra | Format of the current custom data. The value is the resource value of **extra**.| resource | The field name is changed. For details, see [Table 4](#table 4-metadata-examples).| - -### Table 4 metaData examples +**Table 4** metaData examples | Example in the FA Model| Example in the Stage Model| | -------- | -------- | | "meteData": {
"customizeDate": [{
"name": "label",
"value": "string",
"extra": "$string:label",
}]
} | "meteData": [{
"name": "label",
"value": "string",
"resource": "$string:label",
}] | -### Table 5 abilities comparison +**Table 5** abilities comparison | Field Name Under abilities in the FA Model| Field Description| Field Name Under abilities in the Stage Model| Difference| | -------- | -------- | -------- | -------- | diff --git a/en/application-dev/application-models/thread-model-fa.md b/en/application-dev/application-models/thread-model-fa.md index 75401be69c..56cf8c9473 100644 --- a/en/application-dev/application-models/thread-model-fa.md +++ b/en/application-dev/application-models/thread-model-fa.md @@ -6,7 +6,7 @@ There are three types of threads in the FA model: - Main thread -Manages other threads. + Manages other threads. - Ability thread - One ability thread for each ability. @@ -16,7 +16,7 @@ Manages other threads. - Receives messages sent by the worker thread. - Worker thread - + Performs time-consuming operations diff --git a/en/application-dev/application-models/uiability-intra-device-interaction.md b/en/application-dev/application-models/uiability-intra-device-interaction.md index 065cd62fa0..e5a7de3c5a 100644 --- a/en/application-dev/application-models/uiability-intra-device-interaction.md +++ b/en/application-dev/application-models/uiability-intra-device-interaction.md @@ -431,7 +431,7 @@ Ability call is usually used in the following scenarios: - Starting the callee ability in the background - **Table 1** Terms used in the ability call +**Table 1** Terms used in the ability call | **Term**| Description| | -------- | -------- | diff --git a/en/application-dev/application-models/uiability-launch-type.md b/en/application-dev/application-models/uiability-launch-type.md index 70c212ed46..19d7b73402 100644 --- a/en/application-dev/application-models/uiability-launch-type.md +++ b/en/application-dev/application-models/uiability-launch-type.md @@ -159,4 +159,4 @@ The following steps are used as an example. 4. Return to the home screen and open file A again. UIAbility instance 2 is started. - \ No newline at end of file + \ No newline at end of file diff --git a/en/application-dev/application-models/windowextensionability.md b/en/application-dev/application-models/windowextensionability.md index cf2ce01947..294f0207ab 100644 --- a/en/application-dev/application-models/windowextensionability.md +++ b/en/application-dev/application-models/windowextensionability.md @@ -90,23 +90,23 @@ System applications can load the created WindowExtensionAbility through the Abil 3. Set the width and height. The sample code is as follows: -```ts -@Entry -@Component -struct Index { - @State message: string = 'Hello World' - - build() { - Row() { - Column() { - AbilityComponent({ abilityName: "WindowExtAbility", bundleName: "com.example.WindowExtAbility"}) - .width(500) - .height(500) - } - .width('100%') - } - .height('100%') - .backgroundColor(0x64BB5c) - } -} -``` + ```ts + @Entry + @Component + struct Index { + @State message: string = 'Hello World' + + build() { + Row() { + Column() { + AbilityComponent({ abilityName: "WindowExtAbility", bundleName: "com.example.WindowExtAbility"}) + .width(500) + .height(500) + } + .width('100%') + } + .height('100%') + .backgroundColor(0x64BB5c) + } + } + ``` \ No newline at end of file diff --git a/en/application-dev/faqs/faqs-ability.md b/en/application-dev/faqs/faqs-ability.md index bff181efb9..7b3136f70a 100644 --- a/en/application-dev/faqs/faqs-ability.md +++ b/en/application-dev/faqs/faqs-ability.md @@ -213,4 +213,4 @@ The following conditions must be met: 2. The system return key is used. - \ No newline at end of file + \ No newline at end of file diff --git a/en/application-dev/faqs/faqs-language.md b/en/application-dev/faqs/faqs-language.md index 22a450b4c8..34404f5197 100644 --- a/en/application-dev/faqs/faqs-language.md +++ b/en/application-dev/faqs/faqs-language.md @@ -289,4 +289,4 @@ Applicable to: OpenHarmony SDK 3.2.5.5, stage model of API version 9 No. Relational database operations cannot be performed in the worker thread. - \ No newline at end of file + \ No newline at end of file diff --git a/en/application-dev/napi/neural-network-runtime-guidelines.md b/en/application-dev/napi/neural-network-runtime-guidelines.md index 9ae694fc12..e7df99c9f6 100644 --- a/en/application-dev/napi/neural-network-runtime-guidelines.md +++ b/en/application-dev/napi/neural-network-runtime-guidelines.md @@ -488,4 +488,4 @@ The development process of the Neural Network Runtime consists of three phases: The following sample is provided to help you understand how to connect a third-party AI inference framework to the Neural Network Runtime: - [Development Guide for Connecting TensorFlow Lite to NNRt Delegate](https://gitee.com/openharmony/neural_network_runtime/tree/master/example/deep_learning_framework) - + diff --git a/en/application-dev/reference/apis/js-apis-nfcTag.md b/en/application-dev/reference/apis/js-apis-nfcTag.md index 2dbf451d52..765314f3d5 100644 --- a/en/application-dev/reference/apis/js-apis-nfcTag.md +++ b/en/application-dev/reference/apis/js-apis-nfcTag.md @@ -871,4 +871,4 @@ Enumerates the MIFARE Ultralight tag types. | TYPE_UNKNOWN | 0 | Unknown type.| | TYPE_ULTRALIGHT | 1 | MIFARE Ultralight.| | TYPE_ULTRALIGHT_C | 2 | MIFARE Ultralight C.| - + diff --git a/en/application-dev/reference/apis/js-apis-url.md b/en/application-dev/reference/apis/js-apis-url.md index d4d453a596..6430002af2 100755 --- a/en/application-dev/reference/apis/js-apis-url.md +++ b/en/application-dev/reference/apis/js-apis-url.md @@ -910,4 +910,4 @@ let params = new Url.URLSearchParams(url.search.slice(1)); params.append('fod', '3'); console.log(params.toString()); ``` - + diff --git a/en/application-dev/reference/apis/js-apis-worker.md b/en/application-dev/reference/apis/js-apis-worker.md index 58dca3029a..edf8e40583 100644 --- a/en/application-dev/reference/apis/js-apis-worker.md +++ b/en/application-dev/reference/apis/js-apis-worker.md @@ -2212,4 +2212,4 @@ Configuration of the **build-profile.json5** file: } } ``` - + diff --git a/en/application-dev/reference/arkui-ts/ts-container-ability-component.md b/en/application-dev/reference/arkui-ts/ts-container-ability-component.md index b4bb994bf0..8bc469ed95 100644 --- a/en/application-dev/reference/arkui-ts/ts-container-ability-component.md +++ b/en/application-dev/reference/arkui-ts/ts-container-ability-component.md @@ -75,4 +75,4 @@ struct MyComponent { } ``` - \ No newline at end of file + \ No newline at end of file diff --git a/en/device-dev/porting/porting-thirdparty-cmake.md b/en/device-dev/porting/porting-thirdparty-cmake.md index 59402c5f34..d8dfd53c2c 100755 --- a/en/device-dev/porting/porting-thirdparty-cmake.md +++ b/en/device-dev/porting/porting-thirdparty-cmake.md @@ -292,4 +292,4 @@ The following steps show how to configure and modify the toolchains for cross-co If the compilation is successful, a static library file and test cases will be generated in the **build** directory. - + diff --git a/en/device-dev/porting/porting-thirdparty-makefile.md b/en/device-dev/porting/porting-thirdparty-makefile.md index 7108bfc847..f8630dd005 100644 --- a/en/device-dev/porting/porting-thirdparty-makefile.md +++ b/en/device-dev/porting/porting-thirdparty-makefile.md @@ -191,4 +191,4 @@ The procedure for adding the yxml library is almost the same as that for adding | OpenHarmony/third_party/yxml/config.gni | Third-party library compilation configuration file, which can be modified to determine whether the test cases will be used during the building. | | OpenHarmony/third_party/yxml/yxml/ | Directory of the third-party library to be ported. | - + diff --git a/en/device-dev/subsystems/subsys-dfx-overview.md b/en/device-dev/subsystems/subsys-dfx-overview.md index 246375d40c..f0b223ae2b 100644 --- a/en/device-dev/subsystems/subsys-dfx-overview.md +++ b/en/device-dev/subsystems/subsys-dfx-overview.md @@ -35,4 +35,3 @@ Event logging means to collect and log events reported during system running. Th **System event** A system event is an indication of the system status at a given time point during system running. You can use these events to analyze the status change of the system. - diff --git a/en/release-notes/OpenHarmony-v3.2-beta5.md b/en/release-notes/OpenHarmony-v3.2-beta5.md index c00788dab4..3105ba7669 100644 --- a/en/release-notes/OpenHarmony-v3.2-beta5.md +++ b/en/release-notes/OpenHarmony-v3.2-beta5.md @@ -208,4 +208,4 @@ For more information, visit [Samples](https://gitee.com/openharmony/applications | I6BRTS | Invoking the **rdb::executeSql** interface may cause memory leakage.| Memory leakage occurs when the **rdb::executeSql** interface is repeatedly called during initialization. This interface is called only during application initialization, and therefore the impact of memory leakage is controllable.| 2023-02-10| | I6AZ4T | Memory leakage exists for applications with the **\** component.| Memory leakage occurs when the **\** component is repeatedly called at a high frequency. The root cause is that the memory is not reclaimed during the calling of the third-party library flutter. We will first check whether the problem is caused by the open-source flutter component.| 2023-02-10| - + diff --git a/en/release-notes/api-change/v3.2-beta3/changelog-v3.2-beta3.md b/en/release-notes/api-change/v3.2-beta3/changelog-v3.2-beta3.md index 0070fc5fd8..1cf077181a 100644 --- a/en/release-notes/api-change/v3.2-beta3/changelog-v3.2-beta3.md +++ b/en/release-notes/api-change/v3.2-beta3/changelog-v3.2-beta3.md @@ -231,4 +231,3 @@ If the verification rules are not met, an error is reported during compilation. N/A - \ No newline at end of file -- GitLab