Indentation

Author: decebals

_posts/2015-06-01-forms.md

@@ -29,23 +29,23 @@ You may POST Arrays, Lists, or Sets to your `RouteHandler` implementations by us
 
 ```html
 <form>
-  <input name="rainbow[0]" value="Red">
-  <input name="rainbow[1]" value="Orange">
-  <input name="rainbow[2]" value="Yellow">
-  <input name="rainbow[3]" value="Green">
-  <input name="rainbow[4]" value="Blue">
-  <input name="rainbow[5]" value="Indigo">
-  <input name="rainbow[6]" value="Violet">
+    <input name="rainbow[0]" value="Red">
+    <input name="rainbow[1]" value="Orange">
+    <input name="rainbow[2]" value="Yellow">
+    <input name="rainbow[3]" value="Green">
+    <input name="rainbow[4]" value="Blue">
+    <input name="rainbow[5]" value="Indigo">
+    <input name="rainbow[6]" value="Violet">
 </form>
 ```
 
 In this example, Pippo will automatically collect the values into a parameter named *rainbow*.  The *rainbow* parameter may be accessed and transformed to a collection of your choice.
 
 ```java
 POST("/rainbow", routeContext -> {
-  List<String> rainbowList = routeContext.getParameter("rainbow").toList(String.class);
-  Set<String> rainbowSet = routeContext.getParameter("rainbow").toSet(String.class);
-  TreeSet<String> rainbowTreeSet = routeContext.getParameter("rainbow").toCollection(TreeSet.class, String.class);
+    List<String> rainbowList = routeContext.getParameter("rainbow").toList(String.class);
+    Set<String> rainbowSet = routeContext.getParameter("rainbow").toSet(String.class);
+    TreeSet<String> rainbowTreeSet = routeContext.getParameter("rainbow").toCollection(TreeSet.class, String.class);
 }
 ```
 
@@ -64,23 +64,23 @@ Pippo supports overriding the `POST` method used to submit a form through the us
 
 ```html
 <form>
-  <input name="rainbow[3]" value="Gray">
-  <input type="hidden" name="_method" value="PATCH">
+    <input name="rainbow[3]" value="Gray">
+    <input type="hidden" name="_method" value="PATCH">
 </form>
 ```
 
 Pippo will intercept the `_method` parameter specification and route the request to the `PATCH` handler that matches the URL pattern.
 
 ```java
 PATCH("/rainbow", routeContext -> {
-  List<String> patched = routeContext.getParameter("rainbow").toList(String.class);
-  List<String> rainbow = dao.getRainbow();
-  for (int i = 0; i < patched.size(); i++) {
-    if (patched.get(i) != null) {
-      rainbow.set(i, patched.get(i));
+    List<String> patched = routeContext.getParameter("rainbow").toList(String.class);
+    List<String> rainbow = dao.getRainbow();
+    for (int i = 0; i < patched.size(); i++) {
+        if (patched.get(i) != null) {
+            rainbow.set(i, patched.get(i));
+        }
     }
-  }
-  dao.updateRainbow(rainbow);
+    dao.updateRainbow(rainbow);
 }
 ```
 
@@ -92,15 +92,14 @@ Pippo supports POSTing non-form content by specifying `_content_type` and `_cont
 
 ```html
 <form>
-  <input type="hidden" name="_content" value="['Red', 'Orange', 'Yellow', 'Green', 'Blue', 'Indigo', 'Violet']">
-  <input type="hidden" name="_content_type" value="application/json">
-  <input type="hidden" name="_method" value="PUT">
+    <input type="hidden" name="_content" value="['Red', 'Orange', 'Yellow', 'Green', 'Blue', 'Indigo', 'Violet']">
+    <input type="hidden" name="_content_type" value="application/json">
+    <input type="hidden" name="_method" value="PUT">
 </form>
 ```
 
 ```java
 PUT("/rainbow", routeContext -> {
-  List<String> rainbow = routeContext.createEntityFromBody(List.class);
+    List<String> rainbow = routeContext.createEntityFromBody(List.class);
 });
-
 ```