docs: document namespaced view overriding

Author: datamweb

user_guide_src/source/changelogs/v4.7.0.rst

@@ -191,6 +191,8 @@ Libraries
 - **ResponseTrait:** Added ``paginate``` method to simplify paginated API responses. See :ref:`ResponseTrait::paginate() <api_response_trait_paginate>` for details.
 - **Time:** added methods ``Time::addCalendarMonths()`` and ``Time::subCalendarMonths()``
 - **Time:** Added ``Time::isPast()`` and ``Time::isFuture()`` convenience methods. See :ref:`isPast <time-comparing-two-times-isPast>` and :ref:`isFuture <time-comparing-two-times-isFuture>` for details.
+- **View:** Added the ability to override namespaced views (e.g., from modules) by placing a matching file structure within the **app/Views** directory. See :ref:`Overriding Namespaced Views <views-overriding-namespaced-views>` for details.
+
 
 Commands
 ========

user_guide_src/source/outgoing/views.rst

@@ -104,6 +104,38 @@ example, you could load the **blog_view.php** file from **example/blog/Views** b
 
 .. literalinclude:: views/005.php
 
+.. _views-overriding-namespaced-views:
+Overriding Namespaced Views
+===========================
+
+.. versionadded:: 4.7.0
+    Added the ability to override namespaced views via the **app/Views** directory.
+
+You can override a namespaced view by creating a matching directory structure within your main **app/Views** directory.
+This allows you to customize the output of modules or packages without modifying their source code.
+
+For example, assume you have a module named Blog with the namespace ``Example\Blog``. The original view file is located at:
+
+.. code-block:: text
+
+    /modules
+    └── Example
+        └── Blog
+            └── Views
+                └── blog_view.php
+
+To override this view, create a file at the matching path within your application's Views directory:
+
+.. code-block:: text
+
+    /app
+    └── Views
+        └── Example               <-- Matches the first part of namespace
+            └── Blog              <-- Matches the second part of namespace
+                └── blog_view.php <-- Your custom view
+
+Now, when you call ``view('Example\Blog\blog_view')``, CodeIgniter will automatically load your custom view from **app/Views/Example/Blog/blog_view.php** instead of the original view file.
+
 .. _caching-views:
 
 Caching Views