Setting the selected item in angularJS select directive

问题

I have a problem with setting the selected item in angular's select directive. I don't know if this is a bug or a conscious design from the designers of angular. It sure makes the select directive a lot less useful though.

Description:

My app communicates with a REST API to receive an entity from the database. The API dictates that relations of the object are sent with an ID property only so that you can retrieve them in subsequent requests if needed.

Example:

{ id : 1, customerName : "some name", city : {id : 12}}

where city is another entity that can be retrieved through a different REST endpoint using the city id and looks like so:

{ id: 12, name : "New York"}

I need to create a form to edit the customer entity with a dropdown menu with all possible cities so that the user can select the appopriate city from the list. The list must initially display the customer's city as retrieved from the JSON object.

The form looks like this:

 <form>
  <input type="text" ng-model="customer.name"/>
  <select ng-model="customer.city" ng-options="i as i.name for i in cities"></select>
 </form>

And the controller looks like this:

app.controller('MainCtrl', function ($scope, $http) {
    $http.get(serviceurl + 'admin/rest/customer/' + id + "/", {
        params: {"accept": "json"},
        withCredentials: true
    }).then(function (response) {
                $scope.customer = response.data.item;
            });
    $http.get(serviceurl + 'admin/rest/city/', {
        params: {"accept": "json"},
        withCredentials: true
    }).then(function (response) {
                $scope.cities = response.data.items;
                // THIS LINE LOADS THE ACTUAL DATA FROM JSON
                $scope.customer.city = $scope.findCity($scope.customer.city);
            });
    $scope.findCity = function (city) {
        for (var i = 0; i < $scope.cities.length; i++) {
            if ($scope.cities[i].id == city.id) {
                return $scope.cities[i];
            }
        }
    }
});

What should happen: once the full details of the City object are loaded the select directive must set the city that was loaded as the selected item in the list.

What happens: the list displays an empty item and there's no way to initialize the selected item if the selected item from objects outside the array of items.

DEMO of the issue here: http://plnkr.co/edit/NavukDb34mjjnQOP4HE9?p=preview

Is there a solutions for this? Can the selected item be set programmatically in a generic way so that the AJAX calls and select logic be refactored into a reusable AJAX based select widget ?

回答1:

It is as simple as this

<select
    ng-model="item"
    ng-options="item.name for item in items track by item.name">

Then inside you controller:

// all items
$scope.items = [{name: 'a'}, {name: 'b'}, {name: 'c'}];
// set the active one
$scope.item = {name: 'b'};
// or just
$scope.item = $scope.items[1]

Check out the http://docs.angularjs.org/api/ng.directive:select From there:

trackexpr: Used when working with an array of objects. The result of this expression will be used to identify the objects in the array. The trackexpr will most likely refer to the value variable (e.g. value.propertyName).

The rest is just assigning a value to the $scope.item variable and angular will figure out which element should be set as active by checking the item's name property.

回答2:

The reason it doesn't work is that angular expects the objects references to be equal. In your case (the 'select from object' in your plnkr) creates a new object, albeit with the same properties. However, Angular can't know that two different objects represents the same object. You have at least two approaches:

Find the correct city object instance

Instead of setting $scope.customer.city to a new object, find the actual city object from the $scope.cities array. If you're using UnderscoreJs you could do something like:

$scope.customer.city = _.find($scope.cities, function (city) {
    return city.id === theCustomersCity.id;
});

Bind to the city id instead of the city object

Another approach, which might be easier, is to change the ng-model and ng-options directives to match on id instead of object. See working example here.

<select ng-model="customer.cityId" ng-options="i.id as i.name for i in cities"></select>

回答3:

I came accross the same problem. My options and the modeled data both came from separate API calls.

Instead of adding a layer of indirection by using ng-model on the object keys, I ended up writing a simple directive that uses a "proxy" variable.

<select ng-model="customer.city" ng-options="i as i.name for i in cities"></select>

becomes

<select ng-model="customer_cityProxy" ng-options="i.name as i.name for i in cities"></select>

Using a $watch on customer.city and customer_cityProxy, I get the expected behaviour.

There are still a few drawbacks, on being that it only works if the keys are disjoints.

Code is available here: https://github.com/gosusnp/options-proxy

回答4:

Take a look at http://configit.github.io/ngyn/#select_extensions this solution worked for me

来源：https://stackoverflow.com/questions/15326164/setting-the-selected-item-in-angularjs-select-directive

标签

angularjs

angularjs-directive