Merge pull request #1243 from jim-parry/docs/structure2

jim-parry · web-flow · commit a384868d515b · 2018-09-26T00:21:53.000-07:00
Move Response &amp; APIResponseTrait to outgoing section of UG
diff --git a/user_guide_src/source/concepts/http.rst b/user_guide_src/source/concepts/http.rst
@@ -97,7 +97,7 @@ is an object-oriented representation of the HTTP request. It provides everything
 The request class does a lot of work in the background for you, that you never need to worry about.
 The ``isAJAX()`` and ``isSecure()`` methods check several different methods to determine the correct answer.
 
-CodeIgniter also provides a :doc:`Response class </incoming/response>` that is an object-oriented representation
+CodeIgniter also provides a :doc:`Response class </outgoing/response>` that is an object-oriented representation
 of the HTTP response. This gives you an easy and powerful way to construct your response to the client::
 
   use CodeIgniter\HTTP\Response;
diff --git a/user_guide_src/source/helpers/cookie_helper.rst b/user_guide_src/source/helpers/cookie_helper.rst
@@ -37,7 +37,7 @@ The following functions are available:
 	:rtype:	void
 
 	This helper function gives you friendlier syntax to set browser
-	cookies. Refer to the :doc:`Response Library </incoming/response>` for
+	cookies. Refer to the :doc:`Response Library </outgoing/response>` for
 	a description of its use, as this function is an alias for
 	``Response::setCookie()``.
 
diff --git a/user_guide_src/source/incoming/controllers.rst b/user_guide_src/source/incoming/controllers.rst
@@ -250,7 +250,7 @@ as a class property, ``$this->request``.
 
 **Response Object**
 
-The application's main :doc:`Response Instance </incoming/response>` is always available
+The application's main :doc:`Response Instance </outgoing/response>` is always available
 as a class property, ``$this->response``.
 
 **Logger Object**
diff --git a/user_guide_src/source/incoming/index.rst b/user_guide_src/source/incoming/index.rst
@@ -13,6 +13,4 @@ Controllers handle incoming requests.
     message
     request
     incomingrequest
-    response
-    api_responses
     content_negotiation
diff --git a/user_guide_src/source/incoming/message.rst b/user_guide_src/source/incoming/message.rst
@@ -7,7 +7,7 @@ requests and responses, including the message body, protocol version, utilities
 the headers, and methods for handling content negotiation.
 
 This class is the parent class that both the :doc:`Request Class </incoming/request>` and the
-:doc:`Response Class </incoming/response>` extend from. As such, some methods, such as the content
+:doc:`Response Class </outgoing/response>` extend from. As such, some methods, such as the content
 negotiation methods, may apply only to a request or response, and not the other one, but they have
 been included here to keep the header methods together.
 
diff --git a/user_guide_src/source/libraries/curlrequest.rst b/user_guide_src/source/libraries/curlrequest.rst
@@ -54,7 +54,7 @@ Working with the Library
 ************************
 
 Working with CURL requests is simply a matter of creating the Request and getting a
-:doc:`Response object </incoming/response>` back. It is meant to handle the communications. After that
+:doc:`Response object </outgoing/response>` back. It is meant to handle the communications. After that
 you have complete control over how the information is handled.
 
 Making Requests
diff --git a/user_guide_src/source/outgoing/api_responses.rst b/user_guide_src/source/outgoing/api_responses.rst
diff --git a/user_guide_src/source/outgoing/index.rst b/user_guide_src/source/outgoing/index.rst
@@ -11,5 +11,7 @@ View components are used to build what is returned to the user.
     view_cells
     view_renderer
     view_parser
+    response
+    api_responses
     localization
     alternative_php
diff --git a/user_guide_src/source/outgoing/response.rst b/user_guide_src/source/outgoing/response.rst
