From d03dc0a3b64d82f73ccbb8fb57cf7d7bf07d911d Mon Sep 17 00:00:00 2001 From: allard-mx Date: Wed, 1 Feb 2023 20:11:28 +0000 Subject: [PATCH] Run markdownlint-cli2 on docs --- .../indentation-spacing-test.md | 26 ++++++++++--------- .../building-efficient-mobile-apps/_index.md | 2 +- .../native-startup.md | 1 - .../_index.md | 2 +- .../call-rest-action.md | 1 + .../en/docs/releasenotes/studio-pro/9/9.13.md | 2 +- .../en/docs/releasenotes/studio-pro/9/9.14.md | 2 +- 7 files changed, 19 insertions(+), 17 deletions(-) diff --git a/content/en/docs/developerportal/community-tools/contribute-to-the-mendix-documentation/indentation-spacing-test.md b/content/en/docs/developerportal/community-tools/contribute-to-the-mendix-documentation/indentation-spacing-test.md index 2455742b9f7..8b3c879f83b 100644 --- a/content/en/docs/developerportal/community-tools/contribute-to-the-mendix-documentation/indentation-spacing-test.md +++ b/content/en/docs/developerportal/community-tools/contribute-to-the-mendix-documentation/indentation-spacing-test.md @@ -83,19 +83,19 @@ Paragraph text here. Paragraph text here. * unordered list - 1. ordered list - * unordered list + 1. ordered list + * unordered list Paragraph text here. 1. First list item 1. Second list item - * Unordered sub-list. + * Unordered sub-list. 1. Third list item - 1. Ordered sub-list + 1. Ordered sub-list 3. And another item. - Indenting with a tab and a line break works for generic list items, but not elements like code blocks. Tabs get treated as four spaces, regardless of tab settings within an editor. + Indenting with a tab and a line break works for generic list items, but not elements like code blocks. Tabs get treated as four spaces, regardless of tab settings within an editor. {{% alert color="danger" %}} DO NOT USE TABS @@ -106,17 +106,17 @@ DO NOT USE TABS Paragraph text here. * unordered list - 1. ordered list - * unordered list + 1. ordered list + * unordered list Paragraph text here. 1. First list item - * Unordered sub-list. + * Unordered sub-list. 1. Second list item - 1. Ordered sub-list + 1. Ordered sub-list 3. And another item. - Indenting with a tab and trailing spaces works for generic list items, but not elements like code blocks. + Indenting with a tab and trailing spaces works for generic list items, but not elements like code blocks. {{% alert color="danger" %}} DO NOT USE TABS @@ -194,9 +194,9 @@ My alert box My alert box {{% / alert %}} - {{% alert color="warning" %}} Lists in alerts: + 1. First list item 2. Second list item `a code snippet` * Sub-list @@ -204,9 +204,11 @@ Lists in alerts: ``` A code block ``` + {{% / alert %}} ## 2 Use of Markdown Extras + ### 2.1 Block Quotes >A block of text @@ -239,8 +241,8 @@ If you need an element that starts collapsed and can be expanded by clicking, it hidden stuff - The code example of details syntax: + ```html
Description of what is hidden hidden stuff diff --git a/content/en/docs/refguide/mobile/building-efficient-mobile-apps/_index.md b/content/en/docs/refguide/mobile/building-efficient-mobile-apps/_index.md index f9618966ba4..4daecb5e614 100644 --- a/content/en/docs/refguide/mobile/building-efficient-mobile-apps/_index.md +++ b/content/en/docs/refguide/mobile/building-efficient-mobile-apps/_index.md @@ -13,4 +13,4 @@ The following documents will help you understand data syncing, accelerate your a * [Optimizing Native Startup](/refguide/mobile/building-efficient-mobile-apps/native-startup/) – This guide teaches you how to speed up your native app's startup time. * [Logging In Native Apps](/refguide/mobile/building-efficient-mobile-apps/logging/) – In Mendix Studio Pro v9.16 and above, native mobile apps are able to send logs to the [Mendix Runtime](/refguide/runtime/). Read this guide for information on native app logging configuration. -* [Offline-First Data](/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/): native and progressive web apps use an offline database and a synchronization mechanism to replicate data on the client for efficient access and offline capabilities \ No newline at end of file +* [Offline-First Data](/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/): native and progressive web apps use an offline database and a synchronization mechanism to replicate data on the client for efficient access and offline capabilities diff --git a/content/en/docs/refguide/mobile/building-efficient-mobile-apps/native-startup.md b/content/en/docs/refguide/mobile/building-efficient-mobile-apps/native-startup.md index 8e26124140e..681abee3e78 100644 --- a/content/en/docs/refguide/mobile/building-efficient-mobile-apps/native-startup.md +++ b/content/en/docs/refguide/mobile/building-efficient-mobile-apps/native-startup.md @@ -49,4 +49,3 @@ If you need to synchronize files and images on startup, ensure their size is sma If you have configured a nanoflow as a startup nanoflow it may affect your app's startup performance—especially if the nanoflow performs additional data synchronization, excessive data operations on the local device, or microflow calls. We recommend creating short-running startup nanoflows, because native apps keep showing their splash screen until your startup nanoflow executes a **Show page** action. If you must perform long operations in your startup nanoflow, you can show a page at the beginning to help the end-user understand the process. - diff --git a/content/en/docs/refguide/mobile/designing-mobile-user-interfaces/_index.md b/content/en/docs/refguide/mobile/designing-mobile-user-interfaces/_index.md index 0a8315ceff3..1d6748ef6d3 100644 --- a/content/en/docs/refguide/mobile/designing-mobile-user-interfaces/_index.md +++ b/content/en/docs/refguide/mobile/designing-mobile-user-interfaces/_index.md @@ -21,4 +21,4 @@ These documents guide you through the process of shaping great mobile user exper * [Navigation](/refguide/mobile/designing-mobile-user-interfaces/navigation/) – This guide gives general information for native navigation in Mendix test. * [Images, Icons, and Fonts](/refguide/mobile/designing-mobile-user-interfaces/images-icons-and-fonts/) – This guide helps you enrich your native mobile app's design with images and custom fonts. * [Native Styling](/refguide/mobile/designing-mobile-user-interfaces/native-styling/) – This guide gives general information for native styling in Mendix. -* [Widget Styling Guide](/refguide/mobile/designing-mobile-user-interfaces/widget-styling-guide/) – This guide contextualizes the style elements Mendix uses in native mobile apps and explains the classes and style properties of Mendix’s widgets. \ No newline at end of file +* [Widget Styling Guide](/refguide/mobile/designing-mobile-user-interfaces/widget-styling-guide/) – This guide contextualizes the style elements Mendix uses in native mobile apps and explains the classes and style properties of Mendix’s widgets. diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-rest-action.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-rest-action.md index 0f42d150f3a..ed15a42f3de 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-rest-action.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-rest-action.md @@ -225,6 +225,7 @@ This attribute is filled when one of the following scenarios occur: * The **Response handling** is **Store in an HTTP response** and the call succeeded * The **Store message body in $latestHttpResponse variable** option in the **Error handling** section is checked and the call failed * + This variable can only be accessed in the microflow where the **Call REST Service** activity is used. #### 7.3.2 Store Message Body in $latestHttpResponse Variable {#latesthttpresponse} diff --git a/content/en/docs/releasenotes/studio-pro/9/9.13.md b/content/en/docs/releasenotes/studio-pro/9/9.13.md index 1a0fad67c4f..98219bcc99c 100644 --- a/content/en/docs/releasenotes/studio-pro/9/9.13.md +++ b/content/en/docs/releasenotes/studio-pro/9/9.13.md @@ -83,4 +83,4 @@ weight: 87 ### Known Issues * There is a known issue for the scenario where there are multiple instances of the same identical object (meaning, with the same ID) assigned to different microflow variables, this object has a one-to-one association to another entity, and no changes have been made to the associated object. When you then set the association to the same value, only a single microflow variable points correctly to the new association, and the other variables have an empty association. (Ticket 168024) - * Workaround: Do not have multiple microflow variables pointing to the same object instance (for example, pass along the value instead of retrieving it twice from the database). \ No newline at end of file + * Workaround: Do not have multiple microflow variables pointing to the same object instance (for example, pass along the value instead of retrieving it twice from the database). diff --git a/content/en/docs/releasenotes/studio-pro/9/9.14.md b/content/en/docs/releasenotes/studio-pro/9/9.14.md index 5365b87b03d..74f4cc90d76 100644 --- a/content/en/docs/releasenotes/studio-pro/9/9.14.md +++ b/content/en/docs/releasenotes/studio-pro/9/9.14.md @@ -20,7 +20,7 @@ weight: 86 * There is a known issue for the scenario where there are multiple instances of the same identical object (meaning, with the same ID) assigned to different microflow variables, this object has a one-to-one association to another entity, and no changes have been made to the associated object. When you then set the association to the same value, only a single microflow variable points correctly to the new association, and the other variables have an empty association. (Ticket 168024) * Workaround: Do not have multiple microflow variables pointing to the same object instance (for example, pass along the value instead of retrieving it twice from the database). - + ## 9.14.1 {#9141} **Release date: June 14th, 2022**