Change detection not firing with object

[sdornan]

I am using the pipe very similarly to the example given with ngx-filter-pipe v2.0.0 and angular v5.2.5.

Template:

<input type="text" placeholder="Find by name" [(ngModel)]="targetFiltersFilter.name">

<mat-chip-list>
  <mat-chip *ngFor="let target of targetFilters | filterBy: targetFiltersFilter">{{ target.name }}</mat-chip>
</mat-chip-list>

Inside component:

targetFilters: any[] = [{ name: 'aaaa' , selected: false },  { name: 'bbbb', selected: false }, ... ];
targetFiltersFilter: any = { name: '' };

It seems that the pipe isn't being triggered when I type into the input. I can see that the pipe gets triggered once when the page first loads but not at all after that when I modify targetFilterFilter's name attribute via the text field. The pipe does get fired, however, if I change its input to a string value instead of an object, or if I change pure: false in the pipe declaration. This says to me that Angular is doing some type of too shallow comparison for its change detection that doesn't take into account if an object's properties have been modified. Any advice? Would some change within a recent version of angular itself cause this?

Bug Report or Feature Request (mark with an x)

- [ ] Regression (a behavior that used to work and stopped working in a new release)
- [x] Bug report -> please search issues before submitting
- [ ] Feature request
- [ ] Documentation issue or request

[sdornan]

Just found this in the docs:

"Angular ignores changes within (composite) objects. It won't call a pure pipe if you change an input month, add to an input array, or update an input object property."

https://angular.io/guide/pipes#pure-pipes-and-pure-functions

[VadimDez]

Fixed in 2.1.0