Igniteui-angular: Grid remains in pending state after commiting row edit w/o changes

Created on 3 May 2019  路  3Comments  路  Source: IgniteUI/igniteui-angular

Description

Grid w/ [rowEditable]="true" remains in pending transaction state (even when no transaction are enabled) after a commit row editing w/o making changes.

  • igniteui-angular version: 7.2.x, 7.3.x
  • browser: N/A

Steps to reproduce

Open the devSample for Grid Row Editing.
Under the first grid (*Row Editing w/o Transactions):

  1. Enter row editing on the first row and make a change (without exiting)
  2. Click on the Delete button on another row - that row is properly deleted
  3. Enter row editing on the first row and make no change (do not exit)
  4. Click on the Delete button on another row

Result

The row is not deleted and stays in a pending deleted state

Expected result

The row is deleted

Attachments

Invalid state:
image

bug general row-editing regression high resolved transaction 7.2.x 7.3.x

Most helpful comment

@jdk339 this fix is not related to the issue you are facing. Actually the issue you are facing is related to the wrong binding in the sample. I logged this sample issue here. To fix this at your side bind to cell.editValue instead of to cell.value.

All 3 comments

Curious if this will also fix the issue where values changed in custom ng-templates will not trigger a changed row value.

In the StackBlitz sample for the documentation's "Grid Row Editing" page, here is the result after changing a row's UnitsInStock value:

{rowID: 1, oldValue: {鈥, newValue: null, cancel: false鈥

The expected result would be:

{rowID: 1, oldValue: {鈥, newValue: {...}, cancel: false鈥

If this is too unrelated to this issue (#4680), then I can create another issue. It's an extremely important feature for our company, so please fix quickly.

@jdk339 this fix is not related to the issue you are facing. Actually the issue you are facing is related to the wrong binding in the sample. I logged this sample issue here. To fix this at your side bind to cell.editValue instead of to cell.value.

Thanks again, @wnvko. Everything is working fine now.

Was this page helpful?
0 / 5 - 0 ratings