├── .gitignore
├── .npmignore
├── .travis.yml
├── CONTRIBUTING.md
├── Gruntfile.js
├── LICENSE
├── README.md
├── bower.json
├── examples
├── plain
│ └── index.html
└── simple.js
├── package.json
├── src
└── modelFactory.js
└── test
├── .jshintrc
├── karma.conf-ci.js
├── karma.conf.js
└── spec
├── modelFactory.spec.js
├── modelUsage.spec.js
└── regression.spec.js
/.gitignore:
--------------------------------------------------------------------------------
1 | node_modules/
2 | bower_components/
3 | jspm_packages/
4 | .idea/*
5 | _site/
6 | typings/
7 | dist/
8 | *.log
9 |
--------------------------------------------------------------------------------
/.npmignore:
--------------------------------------------------------------------------------
1 | node_modules/
2 | bower_components/
3 | test/
4 | src/
5 | examples/
--------------------------------------------------------------------------------
/.travis.yml:
--------------------------------------------------------------------------------
1 | sudo: false
2 | language: node_js
3 | cache:
4 | directories:
5 | - node_modules
6 | branches:
7 | only:
8 | - master
9 | notifications:
10 | email: false
11 | node_js:
12 | - '4.1'
13 | before_install:
14 | - npm i -g npm@^2.0.0
15 | - npm install -g grunt
16 | - npm install -g bower
17 | - npm install
18 | - bower install
19 | before_script:
20 | - npm prune
21 | after_success:
22 | - npm run semantic-release
23 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | Contributing
2 | ============
3 |
4 | We'd love to get contributions from your part...in the end that's the value behind sharing, right? :smile:
5 | However, for staying organized we'd like you to follow these simple guidelines:
6 |
7 | - [Issues](#issues)
8 | - [Commit Message Guidelines](#commit)
9 | - [Coding](#coding)
10 |
11 | ## Issues
12 |
13 | If you have a bug or enhancement request, please file an issue.
14 |
15 | When submitting an issue, please include context from your test and
16 | your application. If there's an error, please include the error text.
17 |
18 | The best would be to submit a PR with a failing test :smiley:.
19 |
20 | ## Commit Message Guidelines
21 |
22 | These guidelines have been taken and adapted from the [official Angular guidelines](https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-commit-message-guidelines). By following the rules also mentioned in [conventional-changelog](https://www.npmjs.com/package/conventional-changelog). This leads to much more readable and clearer commit messages.
23 |
24 | ### Commit Message Format
25 | Each commit message consists of a **header**, a **body** and a **footer**. The header has a special
26 | format that includes a **type**, a **scope** and a **subject**:
27 |
28 | ```
29 | ():
30 |
31 |
32 |
33 |