Issue 1:
**I pass variable "activeObject$" through input() option in component

Current behavior

vendor.bundle.js:42872 EXCEPTION: Uncaught (in promise): Error: Error in ./BaseObjectReleasesPageComponent class BaseObjectReleasesPageComponent - inline template:170:43 caused by: Failed to execute 'setAttribute' on 'Element': 'ng-reflect-active-object$' is not a valid attribute name.

Error: Failed to execute 'setAttribute' on 'Element': 'ng-reflect-active-object$' is not a valid attribute name.

at DomRenderer.setElementAttribute (http://beta.prwire:4201/vendor.bundle.js:32057:31)

at DomRenderer.setBindingDebugInfo (http://beta.prwire:4201/vendor.bundle.js:32078:18)

at DebugDomRenderer.setBindingDebugInfo (http://beta.prwire:4201/vendor.bundle.js:59773:24)

at setBindingDebugInfo (http://beta.prwire:4201/vendor.bundle.js:19771:18)

at http://beta.prwire:4201/vendor.bundle.js:19763:9

at Array.forEach (native)

at setBindingDebugInfoForChanges (http://beta.prwire:4201/vendor.bundle.js:19762:26)

at Wrapper_EmailSubscriptionsBlockComponent.ngDoCheck (/AppModule/EmailSubscriptionsBlockComponent/wrapper.ngfactory.js:29:7)

at CompiledTemplate.proxyViewClass.View_BaseObjectReleasesPageComponent0.detectChangesInternal (/AppModule/BaseObjectReleasesPageComponent/component.ngfactory.js:264:47)

at CompiledTemplate.proxyViewClass.AppView.detectChanges (http://beta.prwire:4201/vendor.bundle.js:61297:14)

** OS:

Linux user-desktop 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

ng version

angular-cli: 1.0.0-beta.21

node: 7.1.0

os: linux x64

Angular version:

"dependencies": {

"@angular/common": "2.2.3",

"@angular/compiler": "2.2.3",

"@angular/core": "2.2.3",

"@angular/forms": "2.2.3",

"@angular/http": "2.2.3",

"@angular/platform-browser": "2.2.3",

"@angular/platform-browser-dynamic": "2.2.3",

"@angular/router": "3.2.3",

"angular2-cookie": "^1.2.5",

"angular2-toaster": "^1.0.2",

"core-js": "^2.4.1",

"ng2-pagination": "^0.5.1",

"rxjs": "5.0.0-rc.1",

"systemjs": "0.19.41",

"ts-helpers": "^1.1.1",

"zone.js": "^0.6.23"

},

"devDependencies": {

"@angular/compiler-cli": "2.2.3",

"@types/jasmine": "2.5.38",

"@types/node": "^6.0.42",

"angular-cli": "1.0.0-beta.22",

...

Browser: Chrome

Issue 2:
I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[x ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

I have the the following active paths

'./path1' the link path1 should be active.

'./path1?param1=70000&param2=test2' the link path1 should be active.

'./path1/path2' the link path2 should be active.

I am using [routerLinkActiveOptions]="{ exact: true }" to distinguise between './path1' and './path1/path2' but this doesn't work with queryParams. Which is why I should probably use the queryParams variable. But since I want to allow any parameter it's strange that I have to specify all of them.

Expected behavior

path1 should be active even with parameters without needing to specify all of them.

What is the motivation / use case for changing the behavior?

In use cases where there are many parameters and you want to make the link active for any of them it's strange that you need to specify all of them.

Please tell us about your environment:

Angular2 latest, chrome

Angular version: 2.0.X

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Chrome

Language: [all | TypeScript X.X | ES6/7 | ES5]

Typescript