You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2015-03-17-locals.md
+3-7Lines changed: 3 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Locals are good for storing variables for the __CURRENT__ request/response cycle
10
10
These variables are store in [Response]({{ site.coreurl }}/src/main/java/ro/pippo/core/Response.java) and will be available automatically to all templates for the current request/response cycle.
11
11
12
12
```java
13
-
GET("/contact/{id}", (routeContext)-> {
13
+
GET("/contact/{id}", routeContext -> {
14
14
/*
15
15
// variant 1 (with model)
16
16
Map<String, Object> model = new HashMap<>();
@@ -33,14 +33,10 @@ Another scenario for locals:
33
33
34
34
```java
35
35
// filter that injects 'contacts' in locals and implicit in all templates
[RouteContext]({{ site.coreurl }}/src/main/java/ro/pippo/core/route/RouteContext.java) represents the current context of a `Route` being processed by the Pippo.
157
157
It's an object that encapsulates information about the route.
0 commit comments