addHelper() migration docs.

en/appendices/4-1-migration-guide.rst

@@ -51,7 +51,7 @@ Routing
 View
 ----
 
-* ``Form/ContextInteface::primaryKey()`` was deprecated. Use ``getPrimaryKey()``
+* ``Form/ContextInterface::primaryKey()`` was deprecated. Use ``getPrimaryKey()``
   instead.
 
 Behavior Changes
@@ -156,6 +156,7 @@ View
 
 * Added ``TextHelper::slug()``. This method delegates to
   ``Cake\Utility\Text::slug()``.
+* Added ``ViewBuilder::addHelper()`` as chainable wrapper method to add helpers.
 
 Utility
 -------

en/controllers.rst

@@ -199,7 +199,7 @@ theme that will be used when rendering the view, you can use the
 properties of the view before it is created::
 
     $this->viewBuilder()
-        ->setHelpers(['MyCustom'])
+        ->addHelper('MyCustom')
         ->setTheme('Modern')
         ->setClassName('Modern.Admin');
 

en/plugins.rst

@@ -187,10 +187,10 @@ helpers by prefixing the name of the plugin.
 
 For example, say you wanted to use the ContactManager plugin's
 ContactInfoHelper to output formatted contact information in
-one of your views. In your controller, ``setHelpers()``
+one of your views. In your controller, using ``addHelper()``
 could look like this::
 
-    $this->viewBuilder()->setHelpers(['ContactManager.ContactInfo']);
+    $this->viewBuilder()->addHelper('ContactManager.ContactInfo');
 
 .. note::
     This dot separated class name is referred to as :term:`plugin syntax`.

en/views/helpers.rst

@@ -83,7 +83,7 @@ You can also use your controller's ``beforeRender`` method to load helpers::
         public function beforeRender(EventInterface $event)
         {
             parent::beforeRender($event);
-            $this->viewBuilder()->setHelpers(['MyHelper']);
+            $this->viewBuilder()->addHelper('MyHelper');
         }
     }