<p dir="auto">This is a follow up to <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="186020810" data-permission-text="Title is private" data-url="https://github.com/angular/angular/issues/12601" data-hovercard-type="pull_request" data-hovercard-url="/angular/angular/pull/12601/hovercard" href="https://github.com/angular/angular/pull/12601">#12601</a>. Basically, I'd like to find a way to have a flattened view of router params available to components so that each components need not know about how the router tree has been configured. See <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="186020810" data-permission-text="Title is private" data-url="https://github.com/angular/angular/issues/12601" data-hovercard-type="pull_request" data-hovercard-url="/angular/angular/pull/12601/hovercard" href="https://github.com/angular/angular/pull/12601">#12601</a> for an implementation idea.</p>
<p dir="auto"><strong>I'm submitting a ...</strong>  (check one with "x")</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="[x] feature request"><pre class="notranslate"><code class="notranslate">[x] feature request
</code></pre></div>
<p dir="auto"><strong>Current behavior</strong></p>

<p dir="auto">Components would need to manually traverse the tree in order to find parameters defined in router tree.</p>
<p dir="auto"><strong>Expected behavior</strong></p>

<p dir="auto">Components can now be incognizant of the router configuration when finding parameter values.</p>
<p dir="auto"><strong>What is the motivation / use case for changing the behavior?</strong></p>

<p dir="auto">This helps the components consuming ActivatedRoute finding all the parameters defined in the<br>
route, decoupling them from the knowledge of how nested routers are configured.</p>
<ul dir="auto">
<li><strong>Angular version:</strong> 2.0.X</li>
</ul>
<p dir="auto"><strong>I'm submitting a ...</strong>  (check one with "x")</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="[ ] bug report =&gt; search github for a similar issue or PR before submitting
[x] feature request
[x] support request =&gt; Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question"><pre class="notranslate"><code class="notranslate">[ ] bug report =&gt; search github for a similar issue or PR before submitting
[x] feature request
[x] support request =&gt; Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
</code></pre></div>
<p dir="auto"><strong>Current behavior</strong><br>
When using a parametrized route which targets a component, only this component can access those parameters.</p>
<p dir="auto"><strong>Expected/desired behavior</strong><br>
It might be necessary to read the parameters in other components.</p>
<p dir="auto"><strong>Reproduction of the problem</strong><br>
If the current behavior is a bug or you can illustrate your feature request better with an example, please provide the steps to reproduce and if possible a minimal demo of the problem via <a href="https://plnkr.co" rel="nofollow">https://plnkr.co</a> or similar (you can use this template as a starting point: <a href="http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5" rel="nofollow">http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5</a>).<br>
Consider the following route configuration</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="export const routes: RouterConfig = [
 { path: 'confirmation/:hashID', component: ConfirmationComponent, canActivate: [AuthGuard] },
];
"><pre class="notranslate"><code class="notranslate">export const routes: RouterConfig = [
 { path: 'confirmation/:hashID', component: ConfirmationComponent, canActivate: [AuthGuard] },
];

</code></pre></div>
<p dir="auto">Consider the following code as part of the ConfirmationComponent</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="this.activatedRoute.params.subscribe(params =&gt; {
            var hashID = params['hashID'];
        },"><pre class="notranslate"><code class="notranslate">this.activatedRoute.params.subscribe(params =&gt; {
            var hashID = params['hashID'];
        },
</code></pre></div>
<p dir="auto">If I use the above code in any other component, hashID won't be available. It is necessary to read location.path() and extract the hashID value.</p>
<p dir="auto"><strong>What is the expected behavior?</strong><br>
Although I understand that the targeted component it the ConfirmationComponent, sometimes other components might need to have access to the parameters explicitly written in the URL.</p>
<p dir="auto"><strong>What is the motivation / use case for changing the behavior?</strong></p>
<p dir="auto"><strong>Please tell us about your environment:</strong></p>
<ul dir="auto">
<li><strong>Angular version:</strong> 2.0.0-rc.4</li>
<li><strong>Browser:</strong> [<strong>all</strong> | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]</li>
<li><strong>Language:</strong> [all | <strong>TypeScript 1.8</strong> | ES6/7 | <strong>ES5</strong>]</li>
</ul>