pax_global_header00006660000000000000000000000064127033010600014502gustar00rootroot0000000000000052 comment=7d539d4be0e4285fcc756d75064585fff5d9411e assertive-2.1.1/000077500000000000000000000000001270330106000135105ustar00rootroot00000000000000assertive-2.1.1/.editorconfig000066400000000000000000000002531270330106000161650ustar00rootroot00000000000000root = true [*] indent_style = space indent_size = 2 charset = utf-8 trim_trailing_whitespace = true insert_final_newline = true [*.md] trim_trailing_whitespace = false assertive-2.1.1/.gitignore000066400000000000000000000000541270330106000154770ustar00rootroot00000000000000node_modules/ npm-debug.log /tmp *.log *.gz assertive-2.1.1/.npmrc000066400000000000000000000000441270330106000146260ustar00rootroot00000000000000registry=https://registry.npmjs.org assertive-2.1.1/.travis.yml000066400000000000000000000005341270330106000156230ustar00rootroot00000000000000language: node_js node_js: - '0.10' - '4' before_install: - npm install -g npm@latest-2 before_deploy: - 'git config --global user.email "opensource@groupon.com"' - 'git config --global user.name "Groupon"' deploy: provider: script script: ./node_modules/.bin/nlm release skip_cleanup: true 'on': branch: master node: '4' assertive-2.1.1/CHANGELOG.md000066400000000000000000000023701270330106000153230ustar00rootroot00000000000000### 2.1.1 * chore: fix who travis credits for auto-commits - **[@dbushong](https://github.com/dbushong)** [#27](https://github.com/groupon/assertive/pull/27) - [`0ff64b5`](https://github.com/groupon/assertive/commit/0ff64b53cdbdcbe82fe6cf5df21a0255305c0300) **chore:** fix who travis credits for auto-commits ### 2.1.0 * feat: integrate assertive-as-promised functionality - **[@dbushong](https://github.com/dbushong)** [#26](https://github.com/groupon/assertive/pull/26) - [`c9be116`](https://github.com/groupon/assertive/commit/c9be1165235696c773b50b0b80e15ec6bb143633) **feat:** integrate assertive-as-promised functionality ### 2.0.3 * Apply latest nlm generator - **[@i-tier-bot](https://github.com/i-tier-bot)** [#25](https://github.com/groupon/assertive/pull/25) - [`1eb5321`](https://github.com/groupon/assertive/commit/1eb5321691d6ca51287ded93d1ac00bee5037baa) **chore:** Apply latest nlm generator - [`e4939c3`](https://github.com/groupon/assertive/commit/e4939c385b9ca79c0476918b43ae0c917e929004) **fix:** Use lodash 4 method names 2.0.2 ----- * Change Fn.bind to _.partial to support non-ES5 environments - @rduenasf #23 2.0.1 ----- * add coffeelint & npub - @chkhoo #22 * replace underscore & redux with lodash & coffee-script - @chkhoo #21 assertive-2.1.1/CONTRIBUTING.md000066400000000000000000000143231270330106000157440ustar00rootroot00000000000000 # Contributing 🎉🏅 Thanks for helping us improve this project! 🙏 This document outlines some of the practices we care about. If you have any questions or suggestions about the process, feel free to [open an issue](#reporting-issues) . ## How Can I Contribute? ### Reporting Issues If you find any mistakes in the docs or a bug in the code, please [open an issue in Github](https://github.com/groupon/assertive/issues/new) so we can look into it. You can also [create a PR](#contributing-code) fixing it yourself, or course. If you report a bug, please follow these guidelines: * Make sure the bug exists in the latest version. * Include instructions on how to reproduce the issue. The instructions should be as minimal as possible and answer the three big questions: 1. What are the exact steps you took? This includes the exact versions of node, npm, and any packages involved. 1. What result are you expecting? 1. What is the actual result? ### Improving Documentation For small documentation changes, you can use [Github's editing feature](https://help.github.com/articles/editing-files-in-another-user-s-repository/). The only thing to keep in mind is to prefix the commit message with "docs: ". The detault commit message generated by Github will lead to a failing CI build. For larger updates to the documentation it might be better to follow the [instructions for contributing code below](#contributing-code). ### Contributing Code **Note:** If you're planning on making substantial changes, please [open an issue first to discuss your idea](#reporting-issues). Otherwise you might end up investing a lot of work only to discover that it conflicts with plans the maintainers might have. The general steps for creating a pull request are: 1. Create a branch for your change. Always start your branch from the latest `master`. We often prefix the branch name with our initials, e.g. `jk-a-change`. 1. Run `npm install` to install the dependencies. 1. If you're fixing a bug, be sure to write a test *first*. That way you can validate that the test actually catches the bug and doesn't pass. 1. Make your changes to the code. Remember to update the tests if you add new features or change behavior. 1. Run the tests via `npm test`. This will also run style checks and other validations. You might see errors about uncommitted files. This is expected until you commit your changes. 1. Once you're done, `git add .` and `git commit`. Please follow the [commit message conventions](#commits--commit-messages) described below. 1. Push your branch to Github & create a PR. #### Code Style In addition to any linting rules the project might include, a few general rules of thumb: * Try to match the style of the rest of the code. * We prefer simple code that is easy to understand over terse, expressive code. * We try to structure projects by semantics instead of role. E.g. we'd rather have a `tree.js` module that contains tree traversal-related helpers than a `helpers.js` module. * Actually, if you create helpers you might want to put those into a separate package. That way it's easier to reuse them. #### Commits & Commit Messages Please follow the [angular commit message conventions](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#-git-commit-guidelines). We use an automated tool for generating releases that depends on the conventions to determine the next version and the content of the changelog. Commit messages that don't follow the conventions will cause `npm test` (and thus CI) to fail. The short summary - a commit message should look like this: ``` :