angular-chosen

AngularJS Chosen directive

Based on localytics' angular-chosen. Provides some extra directives such as accessing search input value within scope and passing scope variable as placeholder.

This directive brings the Chosen jQuery plugin into AngularJS with ngModel and ngOptions integration.

To use, include "ngChosen" as a dependency in your Angular module. You can now use the "chosen" directive as an attribute on any select element. Angular version 1.2+ is required.

Installation

$ bower install angular-ngchosen

Features

• Works with ngModel and ngOptions
• Supports usage of promises in ngOptions
• Pass scope function via attributes to access search input term.
• Pass placeholder variable via attributes
• Provides a 'loading' animation when 'ngOptions' collection is a promise backed by a remote source
• Pass options to Chosen via attributes or by passing an object to the Chosen directive

Usage

Simple example

Similar to $("#states").chosen()

<select chosen multiple id="states">
  <option value="AK">Alaska</option>
  <option value="AZ">Arizona</option>
  <option value="AR">Arkansas</option>
  <option value="CA">California</option>
</select>

Pass any chosen options as attributes

<select chosen
        data-placeholder="Pick one of these"
        disable-search="true"
        allow-single-deselect="true">
  <option value=""></option>
  <option>This is fun</option>
  <option>I like Chosen so much</option>
  <option>I also like bunny rabbits</option>
</select>

Integration with ngModel and ngOptions

<select multiple
        chosen
        ng-model="state"
        ng-options="s for s in states">
</select>

Note: don't try to use ngModel with ngRepeat. It won't work. Use ngOptions. It's better that way.

Also important: if your ngModel is null or undefined, you must manually include an empty option inside your <select>, otherwise you'll encounter strange off-by-one errors:

<select multiple
        chosen
        ng-model="state"
        ng-options="s for s in states">
  <option value=""></option>
</select>

This annoying behavior is alluded to in the examples in the documentation for ngOptions.

Works well with other AngularJS directives

<select chosen
        ng-model="state"
        ng-options="s for s in states"
        ng-disabled="editable">
</select>

Loading from a remote data source

Include chosen-spinner.css and spinner.gif to show an Ajax spinner icon while your data is loading. If the collection comes back empty, the directive will disable the element and show a default "No values available" message. You can customize this message by passing in noResultsText in your options.

app.js

angular.module('App', ['ngResource', 'ngChosen'])
.controller('BeerCtrl', function($scope) {
  $scope.beers = $resource('api/beers').query()
});

index.html

<div ng-controller="BeerCtrl">
  <select chosen
          data-placeholder="Choose a beer"
          no-results-text="'Could not find any beers :('"
          ng-model="beer"
          ng-options="b for b in beers">
  </select>
</div>

Image of select defined above in loading state:

Note: Assigning promises directly to scope is now deprecated in Angular 1.2+. Assign the results of the promise to scope once the promise returns. The loader animation will still work as long as the collection expression evaluates to undefined while your data is loading!

Access search input term in Angular scope

Html

<div ng-controller="StateCtrl">
    <select chosen
            ng-model="state"
            ng-options="s for s in states"
            input-change-handler="chosenChangeHandler">
    </select>
</div>

Script

angular.module('App', ['ngChosen'])
.controller('StateCtrl', function($scope) {
    $scope.states = ['Alaska','Arizona','Arkansas','California'];

    $scope.chosenChangeHandler = function chosenChangeHandler(val) {
        // set model
        $scope.chosenSearchTerm = val;
    }
});