Merge pull request #4022 from totoprayogo1916/use-short-tag

Update examples

Author: MGatner

user_guide_src/source/cli/cli.rst

@@ -38,15 +38,17 @@ Let's create a simple controller so you can see it in action. Using your
 text editor, create a file called Tools.php, and put the following code
 in it::
 
-    <?php namespace App\Controllers;
+    <?php
+
+    namespace App\Controllers;
 
     use CodeIgniter\Controller;
 
     class Tools extends Controller
     {
         public function message($to = 'World')
         {
-            echo "Hello {$to}!".PHP_EOL;
+            echo "Hello {$to}!" . PHP_EOL;
         }
     }
 

user_guide_src/source/cli/cli_commands.rst

@@ -99,7 +99,9 @@ Let's step through an example command whose only function is to report basic inf
 itself, for demonstration purposes. Start by creating a new file at **/app/Commands/AppInfo.php**. It
 should contain the following code::
 
-    <?php namespace App\Commands;
+    <?php
+
+    namespace App\Commands;
 
     use CodeIgniter\CLI\BaseCommand;
     use CodeIgniter\CLI\CLI;
@@ -112,7 +114,7 @@ should contain the following code::
 
         public function run(array $params)
         {
-
+            // ...
         }
     }
 

user_guide_src/source/cli/cli_library.rst

@@ -20,13 +20,15 @@ Initializing the Class
 You do not need to create an instance of the CLI library, since all of it's methods are static. Instead, you simply
 need to ensure your controller can locate it via a ``use`` statement above your class::
 
-    <?php namespace App\Controllers;
+    <?php
+
+    namespace App\Controllers;
 
     use CodeIgniter\CLI\CLI;
 
     class MyController extends \CodeIgniter\Controller
     {
-        . . .
+        // ...
     }
 
 The class is automatically initialized when the file is loaded the first time.

user_guide_src/source/concepts/autoloader.rst

@@ -71,7 +71,7 @@ by not hitting the file-system with extra ``is_file()`` calls. You can use the c
 third-party libraries that are not namespaced::
 
     $classmap = [
-        'Markdown' => APPPATH .'third_party/markdown.php'
+        'Markdown' => APPPATH . 'third_party/markdown.php'
     ];
 
 The key of each row is the name of the class that you want to locate. The value is the path to locate it at.
@@ -89,7 +89,7 @@ Composer Support
 ================
 
 Composer support is automatically initialized by default. By default, it looks for Composer's autoload file at
-``ROOTPATH.'vendor/autoload.php'``. If you need to change the location of that file for any reason, you can modify
+``ROOTPATH . 'vendor/autoload.php'``. If you need to change the location of that file for any reason, you can modify
 the value defined in ``Config\Constants.php``.
 
 .. note:: If the same namespace is defined in both CodeIgniter and Composer, CodeIgniter's autoloader will be

user_guide_src/source/concepts/factories.rst

@@ -38,7 +38,7 @@ you get back the instance as before::
     class SomeOtherClass
     {
         $widgets = Factories::models('WidgetModel');
-        ...
+        // ...
     }
 
 Factory Parameters
@@ -92,7 +92,9 @@ that supplies options as an array property that matches the name of the componen
 if you wanted to ensure that all Filters used by your app were valid framework instances,
 your **Factories.php** file might look like this::
 
-    <?php namespace Config;
+    <?php
+
+    namespace Config;
 
     use CodeIgniter\Config\Factory as BaseFactory;
     use CodeIgniter\Filters\FilterInterface;

user_guide_src/source/concepts/services.rst

@@ -54,7 +54,7 @@ always return the same instance::
 
 If the creation method requires additional parameters, they can be passed after the service name::
 
-    $renderer = service('renderer', APPPATH.'views/');
+    $renderer = service('renderer', APPPATH . 'views/');
 
 The second function, ``single_service()`` works just like ``service()`` but returns a new instance of
 the class::
@@ -147,15 +147,17 @@ Imagine that you've created a new directory, ``Blog`` in your root directory. Th
 models, etc, and you'd like to make some of the classes available as a service. The first step is to create a new file:
 ``Blog\Config\Services.php``. The skeleton of the file should be::
 
-    <?php namespace Blog\Config;
+    <?php
+
+    namespace Blog\Config;
 
     use CodeIgniter\Config\BaseService;
 
     class Services extends BaseService
     {
         public static function postManager()
         {
-            ...
+            // ...
         }
     }
 

user_guide_src/source/dbmgmt/migration.rst

@@ -47,13 +47,14 @@ migrations go in the **app/Database/Migrations/** directory and have names such
 as *20121031100537_add_blog.php*.
 ::
 
-	<?php namespace App\Database\Migrations;
+	<?php
+
+	namespace App\Database\Migrations;
 
 	use CodeIgniter\Database\Migration;
 
 	class AddBlog extends Migration
 	{
-
 		public function up()
 		{
 			$this->forge->addField([
@@ -64,12 +65,12 @@ as *20121031100537_add_blog.php*.
 					'auto_increment' => true,
 				],
 				'blog_title'       => [
-					'type'           => 'VARCHAR',
-					'constraint'     => '100',
+					'type'       => 'VARCHAR',
+					'constraint' => '100',
 				],
 				'blog_description' => [
-					'type'           => 'TEXT',
-					'null'           => true,
+					'type' => 'TEXT',
+					'null' => true,
 				],
 			]);
 			$this->forge->addKey('blog_id', true);
@@ -117,17 +118,25 @@ another database is used for mission critical data. You can ensure that migratio
 against the proper group by setting the ``$DBGroup`` property on your migration. This name must
 match the name of the database group exactly::
 
-	<?php namespace App\Database\Migrations;
+	<?php
+
+	namespace App\Database\Migrations;
 
 	use CodeIgniter\Database\Migration;
 
 	class AddBlog extends Migration
 	{
 		protected $DBGroup = 'alternate_db_group';
 
-		public function up() { . . . }
+		public function up()
+		{
+			// ...
+		}
 
-		public function down() { . . . }
+		public function down()
+		{
+			// ...
+		}
 	}
 
 Namespaces
@@ -159,11 +168,12 @@ Usage Example
 In this example some simple code is placed in **app/Controllers/Migrate.php**
 to update the schema::
 
-	<?php namespace App\Controllers;
+	<?php
+
+	namespace App\Controllers;
 
 	class Migrate extends \CodeIgniter\Controller
 	{
-
 		public function index()
 		{
 			$migrate = \Config\Services::migrations();
@@ -177,7 +187,6 @@ to update the schema::
 				// Do something with the error here...
 			}
 		}
-
 	}
 
 *******************

user_guide_src/source/extending/basecontroller.rst

@@ -6,12 +6,15 @@ CodeIgniter's core Controller should not be changed, but a default class extensi
 **app/Controllers/BaseController.php**. Any new controllers you make should extend ``BaseController`` to take
 advantage of preloaded components and any additional functionality you provide::
 
-	<?php namespace App\Controllers;
-	
+	<?php
+
+	namespace App\Controllers;
+
 	use CodeIgniter\Controller;
-	
-	class Home extends BaseController {
-	
+
+	class Home extends BaseController
+	{
+		// ...
 	}
 
 Preloading Components

user_guide_src/source/extending/core_classes.rst

@@ -49,13 +49,15 @@ can find your class, that your new class extends the appropriate interface, and
 For example, if you have a new ``App\Libraries\RouteCollection`` class that you would like to use in place of
 the core system class, you would create your class like this::
 
-    <?php namespace App\Libraries;
+    <?php
+
+    namespace App\Libraries;
 
     use CodeIgniter\Router\RouteCollectionInterface;
 
     class RouteCollection implements RouteCollectionInterface
     {
-
+        // ...
     }
 
 Then  you would modify the ``routes`` service to load your class instead::
@@ -81,28 +83,32 @@ identical to replacing a class with one exception:
 
 For example, to extend the native RouteCollection class, you would declare your class with::
 
-    <?php namespace App\Libraries;
+    <?php
+
+    namespace App\Libraries;
 
     use CodeIgniter\Router\RouteCollection;
 
     class RouteCollection extends RouteCollection
     {
-
+        // ...
     }
 
 If you need to use a constructor in your class make sure you extend the parent constructor::
 
-    <?php namespace App\Libraries;
+    <?php
+
+    namespace App\Libraries;
 
     use CodeIgniter\Router\RouteCollection as BaseRouteCollection;
 
     class RouteCollection extends BaseRouteCollection
     {
-         public function __construct()
-         {
-             parent::__construct();
-         }
-     }
+        public function __construct()
+        {
+            parent::__construct();
+        }
+    }
 
 **Tip:**  Any functions in your class that are named identically to the methods in the parent class will be used
 instead of the native ones (this is known as “method overriding”). This allows you to substantially alter the CodeIgniter core.

user_guide_src/source/general/configuration.rst

@@ -64,14 +64,16 @@ The class should use the appropriate namespace, and it should extend
 
 Define the class and fill it with public properties that represent your settings.::
 
-    <?php namespace Config;
+    <?php
+
+    namespace Config;
 
     use CodeIgniter\Config\BaseConfig;
 
     class CustomClass extends BaseConfig
     {
-    	public $siteName  = 'My Great Site';
-    	public $siteEmail = 'webmaster@example.com';
+        public $siteName  = 'My Great Site';
+        public $siteEmail = 'webmaster@example.com';
 
     }
 
@@ -248,7 +250,9 @@ the method named for the configuration class and incorporate any returned proper
 
 A sample configuration class setup for this::
 
-    <?php namespace App\Config;
+    <?php
+
+    namespace App\Config;
 
     use CodeIgniter\Config\BaseConfig;
 
@@ -257,19 +261,24 @@ A sample configuration class setup for this::
         public $target            = 100;
         public $campaign          = "Winter Wonderland";
         public static $registrars = [
-            '\App\Models\RegionalSales';
+            '\App\Models\RegionalSales'
         ];
     }
 
 ... and the associated regional sales model might look like::
 
-    <?php namespace App\Models;
+    <?php
+
+    namespace App\Models;
 
     class RegionalSales
     {
         public static function MySalesConfig()
         {
-            return ['target' => 45, 'actual' => 72];
+            return [
+                'target' => 45,
+                'actual' => 72,
+            ];
         }
     }