fix(transform): modifying transform to match linting rules

doc/en/components/general-changelog-dv-react.md

@@ -495,7 +495,8 @@ Please note that the maximum size available for the icons is 24x24. You can prov
 |37244 | Excel Library | Custom Data Validation is not working.|
 
 ## **{PackageVerChanges-24-2-APR2}**
-> [!Note]With 19.0.0 the React product introduces many breaking changes done to improve and streamline the API. Please refer to the full Update Guide.
+> [!Note]
+> With 19.0.0 the React product introduces many breaking changes done to improve and streamline the API. Please refer to the full Update Guide.
 
 [Update Guide](update-guide.md)
 

doc/en/components/layouts/tile-manager.md

@@ -16,7 +16,8 @@ The following {ProductName} Tile Manager Example shows the component in action.
 
 `sample="/layouts/tile-manager/overview", height="752", scrollable, alt="{Platform} Tile Manager Example"`
 
-> [!Warning] Due to the iframe permissions policy, the fullscreen button in this example will only work when the example is opened in standalone mode by clicking the 'Expand to fullscreen' button in the top-right corner.
+> [!Warning]
+> Due to the iframe permissions policy, the fullscreen button in this example will only work when the example is opened in standalone mode by clicking the 'Expand to fullscreen' button in the top-right corner.
 
 ## Usage
 
@@ -432,7 +433,8 @@ Resizing in the Tile Manager is a functionality that allows tiles to be resized
 
 To ensure smooth resizing, a ghost element is used instead of directly modifying the tile’s dimensions. This element appears on top of the original tile, displaying its current dimensions when resizing begins, and it updates in real time as the user drags any of the resize handles.
 
-> [!Note] If the ghost element exceeds the available grid space, it will automatically adjust to the largest possible span within the grid's limits.
+> [!Note]
+> If the ghost element exceeds the available grid space, it will automatically adjust to the largest possible span within the grid's limits.
 
 The Tile Manager automatically rearranges itself when a tile changes size, ensuring that there is minimal empty space. That's why expanding a tile may push adjacent tiles into new positions, while shrinking creates gaps that other tiles may fill dynamically. This ensures that the Tile Manager stays as compact as possible, without any overlapping tiles, and that all movements remain within the defined grid structure.
 
@@ -499,7 +501,8 @@ You can reorder tiles in the Tile Manager using the drag-and-drop feature. By de
 - With the `tile` option, you can click and hold anywhere on an individual tile to start dragging it.
 - With the `tile-header` option, you can only click and hold in the tile's header section to start the dragging process.
 
-> [!Note] While the tile is in maximized or fullscreen state, the tile cannot be dragged.
+> [!Note]
+> While the tile is in maximized or fullscreen state, the tile cannot be dragged.
 
 Similar to resizing, when you initiate the drag-and-drop process, a ghost element appears beneath the tile you’ve grabbed. As you drag the tile, the ghost element moves with it, dynamically reordering the other tiles in real time. This allows you to preview how the tile grid will look when you drop the tile.
 

doc/jp/components/general-changelog-dv-react.md

@@ -408,7 +408,8 @@ X 軸と Y 軸に `CompanionAxis` プロパティが追加され、既存の軸
 
 ## **{PackageVerChanges-24-2-APR2}**
 
-> [!Note] バージョン 19.0.0 では、React 製品に多くの重大な変更が導入され、API の改善と整理が行われました。詳細は完全なアップデートガイドをご参照ください。
+> [!Note]
+> バージョン 19.0.0 では、React 製品に多くの重大な変更が導入され、API の改善と整理が行われました。詳細は完全なアップデートガイドをご参照ください。
 
 [アップデート ガイド](update-guide.md)
 

src/ext/MarkdownTransformer.ts

@@ -1263,6 +1263,17 @@ function omitPlatformSpecificSections(options: any) {
                                     options.toDelete.add(parent.children[index]);
                                 }
                                 break;
+                            } else if (platformsEqual(currPlats, segment.platforms) && segment.platforms.indexOf(options.platform) != -1) {
+                                // platform matches: keep content but remove the comment markers
+                                parent.children[checkIndex].value = parent.children[checkIndex].value.substring(0, startSeg.startIndex);
+                                if (parent.children[checkIndex].value.length == 0) {
+                                    options.toDelete.add(parent.children[checkIndex]);
+                                }
+                                parent.children[index].value = parent.children[index].value.substring(segment.endIndex);
+                                if (parent.children[index].value.length == 0) {
+                                    options.toDelete.add(parent.children[index]);
+                                }
+                                break;
                             }
                         }
                     }
@@ -1809,7 +1820,7 @@ export class MarkdownTransformer {
             .use(finishRemoveBlocks, options)
             .use(transformNotes, options)
             .use(finishRemoveNotes, options)
-            .use(stringify)
+            .use(stringify, { rule: '-', ruleRepetition: 3, ruleSpaces: false, emphasis: '_', fences: true })
             .process(fileContent, function(err: any, vfile: any) {
                 if (err) {
                     callback(err, null);
@@ -1821,6 +1832,7 @@ export class MarkdownTransformer {
                 fileContent = fileContent.split("*   ").join("- ").split("*  ").join("- "); // unordered lists: "* " -> "- "
                 fileContent = fileContent.split("    - ").join("  - ").split("      - ").join("    - "); // no extra indent
                 fileContent = fileContent.split(".  ").join(". "); // no extra space after item of ordered list
+                fileContent = fileContent.split("\\[!").join("[!"); // note blocks: remark-stringify escapes "[" in "[!NOTE]" as "\[!NOTE]"
 
                 output.push({ content: fileContent, componentOutput: componentOutput });