Igniteui-angular: Events not fired when filter expression/sorting is changed

Created on 7 Oct 2019  路  1Comment  路  Source: IgniteUI/igniteui-angular

Description

Events are not fired when filter expression / sorting is changed (externally)

  • igniteui-angular version: 8.2.x
  • browser: chrome
bug by-design

Most helpful comment

@kdinev
We have already exposed *Change events for two-way binding for all state inputs (including sortingExpressions/filteringExpressionsTree etc.) as part of this issue: https://github.com/IgniteUI/igniteui-angular/issues/3323
Which means we already trigger an event on the related property setters - sortingExpressionsChange/ filteringExpressionsTreeChange.

Depending on what the user wants to achieve he can use those events instead. Triggering the other events as well on the property setters seems redundant.

>All comments

@kdinev
We have already exposed *Change events for two-way binding for all state inputs (including sortingExpressions/filteringExpressionsTree etc.) as part of this issue: https://github.com/IgniteUI/igniteui-angular/issues/3323
Which means we already trigger an event on the related property setters - sortingExpressionsChange/ filteringExpressionsTreeChange.

Depending on what the user wants to achieve he can use those events instead. Triggering the other events as well on the property setters seems redundant.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

nikunjgajera picture nikunjgajera  路  3Comments

ChronosSF picture ChronosSF  路  3Comments

ViktorSlavov picture ViktorSlavov  路  3Comments

QuinntyneBrown picture QuinntyneBrown  路  3Comments

Hypenate picture Hypenate  路  3Comments