From b56718de83135f9278bc80b4da1aa39fe0ab6a5e Mon Sep 17 00:00:00 2001
From: Jennifer Hodgdon <yahgrp@poplarware.com>
Date: Sun, 19 Oct 2014 06:14:11 -0700
Subject: [PATCH] Issue #2359035 by metzlerd: Add info to Routing topic about
 magic placeholder transformation to parameters in method

---
 core/includes/menu.inc | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/core/includes/menu.inc b/core/includes/menu.inc
index c5aae17f3635..76aafd0e0e5e 100644
--- a/core/includes/menu.inc
+++ b/core/includes/menu.inc
@@ -122,6 +122,11 @@
  * As a note, if your module registers multiple simple routes, it is usual
  * (and usually easiest) to put all of their methods on one controller class.
  *
+ * If the route has placeholders (see @ref sec_placeholders above) the
+ * placeholders will be passed to the method (using reflection) by name.
+ * For example, the placeholder '{myvar}' in a route will become the $myvar
+ * parameter to the method.
+ *
  * Most controllers will need to display some information stored in the Drupal
  * database, which will involve using one or more Drupal services (see the
  * @link container Services and container topic @endlink). In order to properly
-- 
GitLab