Description

$scope.deleteSelected = function() {
      var rowsToDelete;
      rowsToDelete = $scope.gridApi.selection.getSelectedRows();
      if (rowsToDelete.length) {
        rowEntity = rowsToDelete[0];
        rowIndexToDelete = $scope.gridOptions.data.indexOf(rowEntity);
        $scope.gridOptions.data.splice(rowIndexToDelete, 1);
      }
   }

Contributor guide

Tech stack

javascriptangular

Domain

frontend

Issue type

bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

AngularJS basicsui grid selection API

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

60

Research direction

Investigate why the grid footer's selected row count is not updated when rows are deleted programmatically using splice. The issue is that splicing gridOptions.data does not trigger the grid's internal selection update. Look at the selection module in ui grid (likely in src/features/selection/) to understand how selected row counts are tracked and updated. The solution may involve using the grid API's deleteRow method or calling gridApi.selection.validateSelection() after data mutation. The plunker linked in the issue provides a reproduction. See if there are any existing tests or PRs related to this.