updated code exmaples to include private var add-on name... also updated example of auto upgrades to add-ons

Author: TomJaeger

docs/development/automated-upgrading.md

@@ -34,9 +34,20 @@ class My_awesome_plugin_upgrade {
 		}
 
 		if(version_compare($version, '4.0.0', '=')) {
-			// Run updates for upgrade to EE3
+			// Run updates for upgrade to EE4
+		}
+
+		if(version_compare($version, '5.0.0', '=')) {
+			// Run updates for upgrade to EE5
 		}
 
+		if(version_compare($version, '6.0.0', '=')) {
+			// Run updates for upgrade to EE6
+		}
+
+		if(version_compare($version, '7.0.0', '=')) {
+			// Run updates for upgrade to EE7
+		}
 	}
 
 }

docs/development/modernizing-existing-add-ons.md

@@ -25,34 +25,41 @@ To utilize the updated method for creating add-ons, you will need to make some s
 [TOC]
 
 ## Updating your mod.addon.php file
-In order to use the new approach, you will have to have your mod file use and extend the module add-on service
+In order to use the new approach, you will have to have your mod file use and extend the module add-on service.  Your mod file will also need to add the protected variable $addon_name in the class
 
 
 ```
 use ExpressionEngine\Service\Addon\Module;
 
-class Addon extends Module
+class Amazing_add_on extends Module
+{
+    protected $addon_name = 'amazing_add_on';
 
 ```
 
+
 ## Updating your mcp.addon.php file
 
-In order to use the new approach, you will have to have your mcp file use and extend the Mcp add-on service
+In order to use the new approach, you will have to have your mcp file use and extend the Mcp add-on service. Your mcp file will also need to add the protected variable $addon_name in the class
 
 ```
 use ExpressionEngine\Service\Addon\Mcp;
 
-class Addon_mcp extends Mcp
+class Amazing_add_on_mcp extends Mcp
+{
+    protected $addon_name = 'amazing_add_on';
 ```
 
 ## Updating your ext.addon.php file
 
-In order to use the new approach, you will have to have your ext file use and extend the Extension add-on service
+In order to use the new approach, you will have to have your ext file use and extend the Extension add-on service.  Your ext file will also need to add the protected variable $addon_name in the class
 
 ```
 use ExpressionEngine\Service\Addon\Extension;
 
-class Addon_ext extends Extension
+class Amazing_add_on_ext extends Extension
+{
+    protected $addon_name = 'amazing_add_on';
 ```
 
 ## Updating your upd.addon.php file
@@ -62,7 +69,8 @@ In order to use the new approach, you will have to have your upd file use and ex
 ```
 use ExpressionEngine\Service\Addon\Installer;
 
-class Addon_upd extends Installer
+class Amazing_add_on_upd extends Installer
+{
 ```
 ## A Note on Plugins
 If your add-on is currently a plugin and you are looking to take advantage of the new add-on development methodologies, we recommend migrating your plugin methods (functions) to your mod file first.  This can be done with a simple copy and paste.

docs/toc_sections/_advanced_usage_toc.yml

@@ -164,6 +164,8 @@
           href: development/widgets.md
         #- name: REMOVE - Adding Text Formatting Options
         #  href: development/text-formatting.md
+    - name: Modernizing add-ons
+      href: development/modernizing-existing-add-ons.md
     - name: Accessing the Database
       href: development/database-access.md
 
@@ -612,8 +614,6 @@
           href: development/guidelines/security.md
         - name: View Files and PHP Syntax
           href: development/guidelines/view-php-syntax.md
-    - name: Modernizing add-ons
-      href: development/modernizing-existing-add-ons.md
     - name: Debugging
       href: development/debugging.md
     - name: v3 Add-on Migration