{"action":"closed","issue":{"url":"https://api.github.com/repos/angular/angular.js/issues/15066","repository_url":"https://api.github.com/repos/angular/angular.js","labels_url":"https://api.github.com/repos/angular/angular.js/issues/15066/labels{/name}","comments_url":"https://api.github.com/repos/angular/angular.js/issues/15066/comments","events_url":"https://api.github.com/repos/angular/angular.js/issues/15066/events","html_url":"https://github.com/angular/angular.js/issues/15066","id":173715595,"number":15066,"title":"Angular 2.0.0-rc5: Changing a chained pipe's parameters doesn't invoke pipes down-chain","user":{"login":"haemaenpaa","id":5008684,"avatar_url":"https://avatars.githubusercontent.com/u/5008684?v=3","gravatar_id":"","url":"https://api.github.com/users/haemaenpaa","html_url":"https://github.com/haemaenpaa","followers_url":"https://api.github.com/users/haemaenpaa/followers","following_url":"https://api.github.com/users/haemaenpaa/following{/other_user}","gists_url":"https://api.github.com/users/haemaenpaa/gists{/gist_id}","starred_url":"https://api.github.com/users/haemaenpaa/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/haemaenpaa/subscriptions","organizations_url":"https://api.github.com/users/haemaenpaa/orgs","repos_url":"https://api.github.com/users/haemaenpaa/repos","events_url":"https://api.github.com/users/haemaenpaa/events{/privacy}","received_events_url":"https://api.github.com/users/haemaenpaa/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-08-29T07:47:02Z","updated_at":"2016-08-29T10:01:15Z","closed_at":"2016-08-29T10:01:15Z","body":"**Do you want to request a *feature* or report a *bug*?**: Bug\r\n\r\n**What is the current behavior?**\r\n\r\nI am attempting to sort the array `users` and split it into pages of 20.\r\n\r\nI have the following template\r\n\r\n   ```\r\n<table class=\"table50\">\r\n  <thead class=\"table_header\">\r\n    <tr>     ...\r\n    </tr>\r\n  </thead>\r\n  <tbody>\r\n    <tr *ngFor=\"let theUser of users | sort: [ sortField, sortAscending ] | paginate: [ pageNumber-1, pageSize ] \">\r\n      <td>{{theUser.id}}</td>\r\n      ...\r\n    </tr>\r\n  </tbody>\r\n</table>\r\n<form *ngIf =\"users && users.length>pageSize\">\r\n  <input type=\"number\" min=\"1\" max=\"{{numPages()}}\" [(ngModel)]=\"pageNumber\" name=\"pg\">/{{numPages()}}\r\n</form>\r\n```\r\n\r\nI use `(click)` to bind clicks on the table header to change `sortField` and/or `sortAscending`, and call `detectChanges()` on an injected `ChangeDetectorRef`. I added a few calls to `console.log` into the two pipes' `transform`  functions, and I noticed that when I click on the header, only the `sort` pipe gets called, and when I change the `pageNumber`, only the `paginate` pipe gets called.\r\n\r\n`sort` is a quicksort, `paginate` outputs the `pageNumber`-th block of `pageSize` objects in the input array.\r\n\r\n**What is the expected behavior?**\r\n\r\nChanging the parameters of `sort` should also cause `paginate` to be run.\r\n\r\n**What is the motivation / use case for changing the behavior?**\r\n\r\nCurrently, changing the parameters of a pipe in the middle of a chain does not change the output seen by the user. I find this counterintuitive, and it is currently forcing me to either write a separate pipe class for any chain of pipes with user-changeable parameters in the middle of the chain.\r\n\r\n**Which versions of Angular, and which browser / OS are affected by this issue?**\r\n\r\nAngular version 2.0.0-rc5\r\nOS: Windows 7 Enterprise Service Pack 1\r\nBrowser: Firefox 45.3.0\r\n"}}
{"actor":{"display_login":"Narretz"}}