From 12d50f2cf52e0d373b83c392b2332cc06289bc15 Mon Sep 17 00:00:00 2001 From: Peter Burns Date: Mon, 3 Oct 2016 09:20:19 -0700 Subject: [PATCH] On a route object, queryParams has underscores Fixes https://github.com/Polymer/docs/issues/1769 --- app/1.0/blog/routing/demo1.html | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/app/1.0/blog/routing/demo1.html b/app/1.0/blog/routing/demo1.html index c5f3f072be..be0fb804e4 100644 --- a/app/1.0/blog/routing/demo1.html +++ b/app/1.0/blog/routing/demo1.html @@ -37,9 +37,13 @@ // Route objects are composed of the `path` that we want to // match on, the `prefix`, which is everything that has already // been matched by someone else before it got to us, and - // a queryParams object, which represents the ?key=value part + // an __queryParams object, which represents the ?key=value part // of the URL. - return {path: '/store/garden', prefix: '', queryParams: {}} + // __queryParams is preceded by underscores because unless you're + // doing the power-user thing of generating your own route objects, + // you want to access query params directly from the + // element. + return {path: '/store/garden', prefix: '', __queryParams: {}} } } }