AngularJS directive for list of checkboxes
In Angular one checkbox <input type="checkbox" ng-model="...">
is linked
with one model.
But in practice we usually want one model to store array of checked values
from several checkboxes.
Checklist-model solves that task without additional code in controller.
You should play with attributes of <input>
tag:
Attribute | Mandatory | Description |
---|---|---|
checklist-model |
Yes | Use instead of ng-model |
checklist-value |
No | What should be picked as array item |
value |
No | What should be picked as item, but unlike checklist-value , this does not evaluate as an angular expression, but rather a static value |
ng-model |
No | Every checkbok will span a new scope and define a variable named checked to hold its state. You can modify this name by using this attribute. |
checklist-comparator |
No | A custom comparator. If it starts with dot(. ) then it will be an expression applied to the array item. Otherwise it should evaluate to a function as an angular expression. The function return true if the first two arguments are equal and false otherwise. |
checklist-before-change |
No | An angular expression evaluated each time before the checklist-model has changed. If it evaluates to 'false' then the model will not change anymore. |
checklist-change |
No | An angular expression evaluated each time the checklist-model has changed. |
- If you modify directly the value of the
checklist-model
, it is possible that the UI won't be updated. This is because this directive looks for the model in the parent, not in the current scope. Instead of doingchecklistModelList = []
it is better to dochecklistModelList.splice(0, checklistModelList.length)
or wrap it in another object. - If you're using
track by
you must specify the same thing forchecklist-value
too. See #46. - If you're also using
ngModel
, please keep in mind that the state of the checkbok is initialized with the value fromchecklistModel
, not with the one fromngModel
. Afterwards the two will be kept in sync, but initially, these two can be conflicting, so onlychecklistModel
is used. See the entire discussion at #104.
Please, try out
- Live demo: http://vitalets.github.io/checklist-model
- JsFiddle basic example (use this to report any issue): http://jsfiddle.net/beradrian/fjoLy5sq/
- JSFiddle required example: http://jsfiddle.net/beradrian/7wt9q1ev/
- Plunkr example: http://plnkr.co/edit/0UrMwtiNQxJJbVWnYgSt?p=preview
- Plunkr example for tree list
- Include the directive in your code
- Download latest release or
- Use bower
bower install checklist-model
or - Install from npm
npm install checklist-model
- If your JavaScript file is not generated from dependencies, then you must include it in your HTML
<script src='checklist-model.js'></script>
- Add to app dependencies:
var app = angular.module("app", ["checklist-model"]);
- Ask a question on StackOverflow and tag it with checklist-model.
- Fill in an issue.
Please keep in mind to also add a Plunkr or JSFiddle example. This will greatly help us in assisting you and you can use one of the existing examples and fork it.
We're using grunt as the build system. grunt jade
generates the demo file and grunt server
starts the demo server that can be access at http://localhost:8000
. Tests can be ran by accessing http://localhost:8000/test
.
The best way to involve is to report an issue/enhancement and then provide a pull request for it using Github usual features.
- Create a new folder under
docs/blocks
namedyour-test
. - Create under that folder
ctrl.js
to describe the test Angular controller,view.html
to describe the view part in HTML andtest.js
for the Angular scenario test. You can use an existing test as an example. - Add a line like
- items.push({id: 'your-test', text: 'Your test, ctrlName: 'CtrlTestName', testValue: 'selectedItems'})
todocs/index.jade
- Add a line like
<script src="../docs/blocks/your-test/test.js"></script>
totest\index.html
- Run
grunt jade
to generateindex.html
fromdocs/index.jade
- Run
grunt server
- Access
http://localhost:8000
for samples andhttp://localhost:8000/test
for running the tests.
- Change the version number in
bower.json
andpackage.json
(if not already changed - check the version number against the latest release in Github) - Create a new release in github with the same name for tag and title as the version number (e.g.
1.0.0
). Do not forget to include the changelog in the release description. - Run
npm publish
to publish the new version to npm
MIT