Home » Angularjs » How do I delete an item or object from an array using ng-click?

How do I delete an item or object from an array using ng-click?

Posted by: admin November 2, 2017 Leave a comment


I am trying to write a function that enables me to remove an item when the button is clicked but I think I am getting confused with the function – do I use $digest?

HTML & app.js:

<ul ng-repeat="bday in bdays">
    <span ng-hide="editing" ng-click="editing = true">{{bday.name}} | {{bday.date}}</span>
    <form ng-show="editing" ng-submit="editing = false">
      <input type="text" ng-model="bday.name" placeholder="Name" ng-required/>
      <input type="date" ng-model="bday.date" placeholder="Date" ng-required/>
      <button class="btn" type="submit">Save</button>
      <a class="btn" ng-click="remove()">Delete</a>

$scope.remove = function(){
  $scope.newBirthday = $scope.$digest();

To remove item you need to remove it from array and can pass bday item to your remove function in markup. Then in controller look up the index of item and remove from array

<a class="btn" ng-click="remove(item)">Delete</a>

Then in controller:

$scope.remove = function(item) { 
  var index = $scope.bdays.indexOf(item);
  $scope.bdays.splice(index, 1);     

Angular will automatically detect the change to the bdays array and do the update of ng-repeat

DEMO: http://plnkr.co/edit/ZdShIA?p=preview

EDIT: If doing live updates with server would use a service you create using $resource to manage the array updates at same time it updates server


This is a correct answer:

<a class="btn" ng-click="remove($index)">Delete</a>

In @charlietfl’s answer. I think it’s wrong since you pass $index as paramter but you use the wish instead in controller. Correct me if I’m wrong 🙂


Using $index works perfectly well in basic cases, and @charlietfl’s answer is great. But sometimes, $index isn’t enough.

Imagine you have a single array, which you’re presenting in two different ng-repeat’s. One of those ng-repeat’s is filtered for objects that have a truthy property, and the other is filtered for a falsy property. Two different filtered arrays are being presented, which derive from a single original array. (Or, if it helps to visualize: perhaps you have a single array of people, and you want one ng-repeat for the women in that array, and another for the men in that same array.) Your goal: delete reliably from the original array, using information from the members of the filtered arrays.

In each of those filtered arrays, $index won’t be the index of the item within the original array. It’ll be the index in the filtered sub-array. So, you won’t be able to tell the person’s index in the original people array, you’ll only know the $index from the women or men sub-array. Try to delete using that, and you’ll have items disappearing from everywhere except where you wanted. What to do?

If you’re lucky enough be using a data model includes a unique identifier for each object, then use that instead of $index, to find the object and splice it out of the main array. (Use my example below, but with that unique identifier.) But if you’re not so lucky?

Angular actually augments each item in an ng-repeated array (in the main, original array) with a unique property called $$hashKey. You can search the original array for a match on the $$hashKey of the item you want to delete, and get rid of it that way.

Note that $$hashKey is an implementation detail, not included in the published API for ng-repeat. They could remove support for that property at any time. But probably not. 🙂

$scope.deleteFilteredItem = function(hashKey, sourceArray){
  angular.forEach(sourceArray, function(obj, index){
    // sourceArray is a reference to the original array passed to ng-repeat, 
    // rather than the filtered version. 
    // 1. compare the target object's hashKey to the current member of the iterable:
    if (obj.$$hashKey === hashKey) {
      // remove the matching item from the array
      sourceArray.splice(index, 1);
      // and exit the loop right away

Invoke with:

ng-click="deleteFilteredItem(item.$$hashKey, refToSourceArray)"

EDIT: Using a function like this, which keys on the $$hashKey instead of a model-specific property name, also has the significant added advantage of making this function reusable across different models and contexts. Provide it with your array reference, and your item reference, and it should just work.


in case you’re inside an ng-repeat

you could use a one liner option

    <div ng-repeat="key in keywords"> 
        <button ng-click="keywords.splice($index, 1)">


$index is used by angular to show current index of the array inside an ng-repeat


Building on the accepted answer, this will work with ngRepeat, filterand handle expections better:


vm.remove = function(item, array) {
  var index = array.indexOf(item);
    array.splice(index, 1);




I usually write in such style :

<a class="btn" ng-click="remove($index)">Delete</a>

$scope.remove = function(index){
  $scope[yourArray].splice(index, 1)

Hope this will help


I disagree that you should be calling a method on your controller. You should be using a service for any actual functionality, and you should be defining directives for any functionality for scalability and modularity, as well as assigning a click event which contains a call to the service which you inject into your directive.

So, for instance, on your HTML…

<a class="btn" ng-remove-birthday="$index">Delete</a>

Then, create a directive…

angular.module('myApp').directive('ngRemoveBirthday', ['myService', function(myService){
    return function(scope, element, attrs){
        angular.element(element.bind('click', function(){
            myService.removeBirthday(scope.$eval(attrs.ngRemoveBirthday), scope);  

Then in your service…

angular.module('myApp').factory('myService', [function(){
    return {
        removeBirthday: function(birthdayIndex, scope){

When you write your code properly like this, you will make it very easy to write future changes without having to restructure your code. It’s organized properly, and you’re handling custom click events correctly by binding using custom directives.

For instance, if your client says, “hey, now let’s make it call the server and make bread, and then popup a modal.” You will be able to easily just go to the service itself without having to add or change any of the HTML, and/or controller method code. If you had just the one line on the controller, you’d eventually need to use a service, for extending the functionality to the heavier lifting the client is asking for.

Also, if you need another ‘Delete’ button elsewhere, you now have a directive attribute (‘ng-remove-birthday’) you can easily assign to any element on the page. This now makes it modular and reusable. This will come in handy when dealing with the HEAVY web components paradigm of Angular 2.0. There IS no controller in 2.0. 🙂

Happy Developing!!!


Here is another answer. I hope it will help.

<a class="btn" ng-click="delete(item)">Delete</a>

 var index = this.list.indexOf(item);
                this.list.splice(index, 1);   

array.splice(start, deleteCount)
array.splice(start, deleteCount, item1, item2, ...)

Full source is here


implementation Without a Controller.

<!DOCTYPE html>
<script src="https://ajax.googleapis.com/ajax/libs/angularjs/1.6.4/angular.min.js"></script>

  var app = angular.module("myShoppingList", []); 

<div ng-app="myShoppingList"  ng-init="products = ['Milk','Bread','Cheese']">
    <li ng-repeat="x in products">{{x}}
      <span ng-click="products.splice($index,1)">×</span>
  <input ng-model="addItem">
  <button ng-click="products.push(addItem)">Add</button>

<p>Click the little x to remove an item from the shopping list.</p>


The splice() method adds/removes items to/from an array.

array.splice(index, howmanyitem(s), item_1, ....., item_n)

Required. An integer that specifies at what position to add/remove items, Use negative values to specify the position from the end of the array.

howmanyitem(s): Optional. The number of items to be removed. If set to 0, no items will be removed.

item_1, …, item_n: Optional. The new item(s) to be added to the array