update

Author: Plaristote

getting-started/index.html

@@ -103,7 +103,7 @@ <h3>2.2 Creating the Blog application</h3>
   </tr>
   <tr>
     <td>config/</td>
-    <td>Configure your application's database, <a href="../request_pipeline">request pipeline</a> and several optional features of Crails.</td>
+    <td>Configure your application's server, database, <a href="../request_pipeline">request pipeline</a> and several optional features of Crails.</td>
   </tr>
   <tr>
     <td>lib/</td>
@@ -231,10 +231,10 @@ <h3>3.2 Say "Hello", Crails</h3>
 </p>
 
 <pre class="filepath">app/routes.cpp</pre>
-<pre><code class="language-cpp">#include &lt;crails/router.hpp&gt;
+<pre><code class="language-cpp">#include "config/router.hpp"
 #include "controllers/welcome.hpp"
 
-void Crails::Router::initialize()
+ApplicationRouter::ApplicationRouter()
 {
   match_action("GET", "/", WelcomeController, index);
 }
@@ -408,9 +408,9 @@ <h3>4.2 Creating an MVC resource</h3>
 <pre class="filepath">app/routes.cpp</pre>
 <pre><code class="language-cpp">#include "app/controllers/article.hpp"
 #include "app/controllers/welcome.hpp"
-#include &lt;crails/router.hpp&gt;
+#include "config/router.hpp"
 
-void Crails::Router::initialize()
+ApplicationRouter::ApplicationRouter()
 {
   resource_actions(article, ArticleController);
   match_action("GET", "/", WelcomeController, index);
@@ -1025,9 +1025,9 @@ <h3>6.2 Adding a route for comments</h3>
 <pre><code class="language-cpp">#include "app/controllers/comment.hpp" // Add comment controller include
 #include "app/controllers/article.hpp"
 #include "app/controllers/welcome.hpp"
-#include &lt;crails/router.hpp&gt;
+#include "config/router.hpp"
 
-void Crails::Router::initialize()
+ApplicationRouter::ApplicationRouter()
 {
   resource_actions(article, ArticleController);
   scope("article/:article_id", [this]()

request_pipeline/index.html

@@ -41,17 +41,15 @@ <h2>1. Introduction</h2>
 #include &lt;crails/request_parsers/url_parser.hpp&gt;
 #include &lt;crails/request_parsers/form_parser.hpp&gt;
 #include &lt;crails/request_parsers/multipart_parser.hpp&gt;
+#include "server.hpp"
 
 using namespace Crails;
 
-const std::string Server::temporary_path = "/tmp";
-
-void Server::initialize_request_pipe()
+void ApplicationServer::initialize_request_pipe()
 {
   add_request_parser(new RequestUrlParser);
   add_request_parser(new RequestFormParser);
   add_request_parser(new RequestMultipartParser);
-
   add_request_handler(new ActionRequestHandler);
   add_request_handler(new FileRequestHandler);
 }
@@ -76,12 +74,11 @@ <h3>1.1 Adding support for queries in json format</h3>
 
 <pre><code class="language-cpp">#include &lt;crails/request_parsers/json_parser.hpp&gt;
 #include &lt;crails/request_handlers/action.hpp&gt;
+#include "server.hpp"
 
 using namespace Crails;
 
-const std::string Server::temporary_path = "/tmp";
-
-void Server::initialize_request_pipe()
+void ApplicationServer::initialize_request_pipe()
 {
   add_request_parser(new RequestJsonParser);
   add_request_handler(new ActionRequestHandler);
@@ -127,7 +124,8 @@ <h2>2. Writing your own request handler</h2>
 </code></pre>
 
 <p>
-  Simple stuff, really: overload <code>operator()</code>, receive a <code>Crails::Context</code>
+  Simple stuff, really: overload <code>operator()</code>, receive a 
+  <a href="https://crails-framework.github.io/api-reference/#/classes/::Crails::Context" target="_blank">Crails::Context</a>
   and a callback object.
 </p>
 <p>
@@ -424,24 +422,15 @@ <h3>3.3 Fill in the Params object</h3>
 
   load_yaml_tree(node, context.params);
 }
-CPP ).to_s); _erbout.&lt;&lt; "
+</code></pre>
 
-&lt;p&gt;
-  Now there's still an issue remaining: if the parsing fail, &lt;code&gt;YAML::Load&lt;/code&gt; will throw an
+<p>
+  Now there's still an issue remaining: if the parsing fail, <code>YAML::Load</code> will throw an
   exception, and our server will respond with an error 500. That would be inaccurate, as the error
-  lies in the query. Let's update our &lt;code&gt;body_received&lt;/code&gt; method to handle parsing errors:
-&lt;/p&gt;
-
-".freeze
-
-
-
-
-
-
+  lies in the query. Let's update our <code>body_received</code> method to handle parsing errors:
+</p>
 
-; _erbout.&lt;&lt;(( code_block &lt;&lt;CPP
-void MyRequestParser::body_received(Crails::Context&amp; context, const std::string&amp; body) const
+<pre><code class="language-cpp">void MyRequestParser::body_received(Crails::Context&amp; context, const std::string&amp; body) const
 {
   try
   {

tutorials/layouts/index.html

@@ -214,7 +214,7 @@ <h3>2.3 Sharing variables with a view</h3>
 
   void index()
   {
-    vars["message"] = std::string("Howdy, little birdie !");
+    vars["message"] = "Howdy, little birdie !";
     render("home/index");
   }
 };
@@ -223,9 +223,13 @@ <h3>2.3 Sharing variables with a view</h3>
 </code></pre>
 
 <p>
-  Note how we explicitely created a <code>std::string</code> when assignin the variable: that's
-  because our template specify the <code>std::string</code> type for the message variable, rather
-  than the <code>const char*</code> type.
+  Note that in this example, <code>"Howdy, little birdie !"</code> has the <code>const char*</code>
+  type, which does not match the variable <code>std::string</code> type we set for the <i>message</i>
+  variable in our template.<br>
+  With any other types, this would be a mistake: you need to be careful that the rvalue you assign
+  to a shared variable is exactly the same as the template's. However, Crails will automatically
+  convert between <code>std::string</code>, <code>std::string_view</code> and <code>const char*</code>,
+  making this example valid.
 </p>
 
 <p>
@@ -246,7 +250,7 @@ <h3>2.3 Sharing variables with a view</h3>
   void index()
   {
     render("home/index", {
-      {"message", std::string("Howdy, little birdie !")}
+      {"message", "Howdy, little birdie !"}
     });
   }
 };
@@ -331,7 +335,7 @@ <h3>3.2 Setting a default layout</h3>
 public:
   HomeController(Crails::Context&amp; context) : Crails::Controller(context)
   {
-    vars["layout"] = std::string("home/my_layout");
+    vars["layout"] = "home/my_layout";
   }
 
   void index()
@@ -350,7 +354,7 @@ <h3>3.2 Setting a default layout</h3>
 <pre><code class="language-cpp">  void index()
   {
     render("home/index", {
-      {"layout", std::string("home/my_layout")}
+      {"layout", "home/my_layout"}
     });
   }
 </code></pre>

tutorials/mail/index.html

@@ -209,22 +209,14 @@ <h4>2.1.3 Recipient options</h4>
   mail.add_recipient("[email protected]", "Jean Piaget", Crails::Mail::CarbonCopy);
   return mail;
 }
-).to_s); _erbout.&lt;&lt; "
+</code></pre>
 
-&lt;p&gt;
+<p>
   Moreover, you may also want some recipients to be hidden from other recipients. This is called
-  &lt;i&gt;Blind Carbon Copy&lt;/i&gt;, and is supported with the &lt;code&gt;Crails::Mail::Blind&lt;/code&gt; option:
-&lt;/p&gt;
-
-".freeze
-
-
-
-
-
+  <i>Blind Carbon Copy</i>, and is supported with the <code>Crails::Mail::Blind</code> option:
+</p>
 
-; _erbout.&lt;&lt;(( code_block &lt;&lt;CPP
-#include &lt;crails/mail.hpp&gt;
+<pre><code class="language-cpp">#include &lt;crails/mail.hpp&gt;
 
 Crails::Mail make_mail()
 {

tutorials/routing/index.html

@@ -55,11 +55,11 @@ <h3>1.2 Configuring the Crails Router</h3>
   and typically look like this:
 </p>
 
-<pre><code class="language-cpp">#include &lt;crails/router.hpp&gt;
+<pre><code class="language-cpp">#include "config/router.hpp"
 #include "controllers/brands.hpp"
 #include "controllers/products.hpp"
 
-void Crails::Router::initialize()
+ApplicationRouter::ApplicationRouter()
 {
   match_action("GET", "brands", Brands, index);
   scope("brands/:brand_id", [&amp;]()
@@ -87,7 +87,7 @@ <h3>1.3 Using the router without controllers</h3>
   callback();
 }
 
-void Crails::Router::initialize()
+ApplicationRouter::ApplicationRouter()
 {
   match("GET", "hello_world", hello_world);
 }