Table (view) is not update when the rows are updated

I’m submitting a … (check one with “x”)

[ X] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here

Current behavior

I’ve a table which I update using a method like newRow

newRow(){
  this.rows.unshift({
      price: 100,
      duration: 60,
      state: 1,
     });
}

where

<datatable #datatableTeaching class="material" 
            [rows]="rows" 
            [columnMode]="'force'"
            [headerHeight]="auto"
            [rowHeight]="'auto'"
            [footerHeight]="'auto'"
            >
....

But the view (table) is not update since that I resize the window. Although the element is pushing in the array.

The problem is the same when I remove the element from the row.

Expected behavior

The view (table) and the array is updated with a new element.

Reproduction of the problem

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

I need update a table in real time for user interaction, which works in the old version 0.6.1.

• Table version: 1.2

• Angular version: 2.0.1

• Browser: [all ]

• Language: [all]

[elvisbegovic]

@amcdnl from my class I use @ViewChild('datatable') datatable; then I refresh using this.datatable.refresh() after delete row but … nothing’s happend … it doesn’t refresh, why ?

PS: in fact when I delete or edit and after that if I resize window or scroll inside datatable a litle bit …my data are updated !! why this behavior , here’s my gif

[shattar]

This is definitely the way ng2 is intended to work, however, it feels a bit awkward for this particular component… seeing as how the main function is to render an array to the screen.

See the comments on issue #32. The filter demo method has some other undesirable side effects, I mean… it filters properly, but… sort the list, then type in a filter, sorting breaks.

Kind of caught between a rock and a hard place. We want OnPush for efficient change detection, but that will cause us to create copies of the row data on every update, which is not efficient, and currently doesn’t function really well anyway. It would be nice if there were a cheaper way to tell the component to check for change. It would also be nice if this components state information were not stored in the applications input rows, so that when a new array is given, the state information is not lost.