Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Angular injects "string:" before value in ng-options

I have a ng-options list defined with a HTML select element such as:

<select
    required="required"
    ng-model="vm.selectedOption"
    ng-options="item.name as item.label for item in vm.options">

    <option value="">Select an option</option>
</select>

This however results in the following HTML:

<option value="string:VALUE" label="Option Name">Option Name</option>

I am using Angular version 1.4.8, does anyone have a solution how to solve the string: issue or at least can explain to me why this is occurring?

The vm.options array looks like this:

[
  {
    "name": "INFILL_AUTOMATIC",
    "label": "Automatic"
  },
  {
    "name": "INFILL_GRID",
    "label": "Grid"
  }
]

//EDIT:

When logging vm.selectedOption I just see the correct value. So the ng-model does in fact have the correct value. But why is Angular giving the default value then this prefix, is it using this prefix to define the "type" for the ng-model or something?

like image 488
Bouke Avatar asked Jan 19 '16 18:01

Bouke


People also ask

How do I set default selected value in ng-options?

Use ng-init to set default value for ng-options .

What is the difference between Ng-options and Ng-repeat?

ng-repeat creates a new scope for each iteration so will not perform as well as ng-options. For small lists, it will not matter, but larger lists should use ng-options. Apart from that, It provides lot of flexibility in specifying iterator and offers performance benefits over ng-repeat.

What does it mean when the value of the selected menu option is an empty string?

The value, when set to the empty string is simply discarded.

How does ng select work?

The ng-selected directive sets the selected attribute of an <option> element in a <select> list. The option will be selected if the expression inside the ng-selected attribute returns true. The ng-selected directive is necessary to be able to shift the value between true and false .


2 Answers

This behavior is documented in the angular changelogs, as a breaking change for Angular 1.4-beta.0. https://github.com/angular/angular.js/blob/master/CHANGELOG.md#breaking-changes-17

Basically, in order to preserve duplicate checking within ng-options, if a list of primitive values are supplied to ng-options, the value's type is prepended to the value in order to create a unique hash key to track (this differs from earlier versions of angular, which would track by the index or the key of the item in the collection).

In practice, this should not affect most usages of ng-options. If it is important for you to preserve the value parameter of the dropdown, you can use the track by parameter in ng-options in order to provide an alternate key to be used for duplicate tracking.

Note that this differs from ng-repeat, in that ng-repeat cannot generate a surrogate key using this method, since it would affect the behavior of the repeated elements. Therefore if a duplicated list is passed to ng-repeat without a track by clause, ng-repeat will produce an error and not render the items, where ng-options is able to render the list.

like image 146
Claies Avatar answered Oct 20 '22 13:10

Claies


Here is the working Plunker

And JS:

    <select ng-model="template"    ng-options="c as (c.label + ' - ' + c.name) for c in options">
like image 24
Sajeetharan Avatar answered Oct 20 '22 11:10

Sajeetharan