Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: console.warn() rather than throwing errors when api signatures are incorrect #804

Merged
merged 6 commits into from Feb 26, 2017
Merged

fix: console.warn() rather than throwing errors when api signatures are incorrect #804

merged 6 commits into from Feb 26, 2017

Commits on Feb 26, 2017

  1. chore: add tests, get coverage back up to 100%

    Benjamin Coe committed Feb 26, 2017
    Copy the full SHA
    27cb94a View commit details
    Browse the repository at this point in the history

  2. fix: switching invalid arguments to warn rather than throw

    Benjamin Coe committed Feb 26, 2017
    Copy the full SHA
    6e0fd0c View commit details
    Browse the repository at this point in the history

  3. fix: converted argsert tests from throws to warnings

    @pahdo
    pahdo authored and Benjamin Coe committed Feb 26, 2017
    Copy the full SHA
    4387f03 View commit details
    Browse the repository at this point in the history

  4. fix: we were no longer using expect

    Benjamin Coe committed Feb 26, 2017
    Copy the full SHA
    200f8e2 View commit details
    Browse the repository at this point in the history

  5. chore: always console.warn()

    Benjamin Coe committed Feb 26, 2017
    Copy the full SHA
    b54a1c2 View commit details
    Browse the repository at this point in the history

  6. fix: merge-conflict, somehow ended up with two copies of default comm… 

    …and tests
    Benjamin Coe committed Feb 26, 2017
    Copy the full SHA
    ee36008 View commit details
    Browse the repository at this point in the history