From be6e41481fde70a5bd4857ca3a47c832ae23e3b3 Mon Sep 17 00:00:00 2001 From: "Chandru(Z0199)" Date: Wed, 12 Feb 2020 21:19:58 +0530 Subject: [PATCH 1/3] Sequence node added in module.xml example --- .../extension-coding/example-module-adminpage.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/guides/v2.3/ext-best-practices/extension-coding/example-module-adminpage.md b/src/guides/v2.3/ext-best-practices/extension-coding/example-module-adminpage.md index a0ef6035166..168d2041624 100644 --- a/src/guides/v2.3/ext-best-practices/extension-coding/example-module-adminpage.md +++ b/src/guides/v2.3/ext-best-practices/extension-coding/example-module-adminpage.md @@ -90,6 +90,9 @@ For more information see: [naming your component]({{ page.baseurl }}/extension-d + + + ``` @@ -102,6 +105,16 @@ If your module does not implement [Declarative Schema]({{ page.baseurl }}/extens ``` +If your module has dependency with other modules, you can change the loading order sequence of the module by using `sequence` node. In below example, `MyCompany_ExampleAdminNewPage` will be load after `Magento_Checkout` module. + +```xml + + + + + +``` + ## Routing and navigation Before we can view the module's page, we need a way to navigate to it. These files create a link to the page in the left navigation and tells Magento how to resolve requests for that page. From 7742c4dafc9f50163d5da02a81a2cde39d2690b6 Mon Sep 17 00:00:00 2001 From: "Chandru(Z0199)" Date: Wed, 12 Feb 2020 21:22:29 +0530 Subject: [PATCH 2/3] Sequence node added in module.xml example --- .../extension-coding/example-module-adminpage.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/src/guides/v2.3/ext-best-practices/extension-coding/example-module-adminpage.md b/src/guides/v2.3/ext-best-practices/extension-coding/example-module-adminpage.md index 168d2041624..35cabbc91ad 100644 --- a/src/guides/v2.3/ext-best-practices/extension-coding/example-module-adminpage.md +++ b/src/guides/v2.3/ext-best-practices/extension-coding/example-module-adminpage.md @@ -90,9 +90,6 @@ For more information see: [naming your component]({{ page.baseurl }}/extension-d - - - ``` From 57805026d9acff3280a9eb3ecb858d059e27628f Mon Sep 17 00:00:00 2001 From: Donald Booth Date: Wed, 12 Feb 2020 13:11:49 -0600 Subject: [PATCH 3/3] Formatting --- .../extension-coding/example-module-adminpage.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/guides/v2.3/ext-best-practices/extension-coding/example-module-adminpage.md b/src/guides/v2.3/ext-best-practices/extension-coding/example-module-adminpage.md index 35cabbc91ad..4ddf5dddb9b 100644 --- a/src/guides/v2.3/ext-best-practices/extension-coding/example-module-adminpage.md +++ b/src/guides/v2.3/ext-best-practices/extension-coding/example-module-adminpage.md @@ -102,7 +102,8 @@ If your module does not implement [Declarative Schema]({{ page.baseurl }}/extens ``` -If your module has dependency with other modules, you can change the loading order sequence of the module by using `sequence` node. In below example, `MyCompany_ExampleAdminNewPage` will be load after `Magento_Checkout` module. +If your module has a dependency with other modules, you can change the loading order sequence of the module by using the `sequence` node. +In the example below, `MyCompany_ExampleAdminNewPage` will be loaded after the `Magento_Checkout` module. ```xml