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.

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

Style/standard #163

Merged
merged 11 commits into from
Feb 10, 2017
Merged

Style/standard #163

merged 11 commits into from
Feb 10, 2017

Conversation

jackboberg
Copy link
Contributor

@jackboberg jackboberg commented Feb 6, 2017

I tried to make this easy to follow along commit by commit, since it will require a lot of review if you tried just looking at the changes..

  • test locally as much as possible

adds `npm run unit` as a discrete method to run just the tests
These changes are primarily:

    > standard --fix

I also cleaned up some of the safe decisions like `one-var` and
`operator-linebreak`. There are still standard errors in this commit:

    > npm run lint | wc -l
    standard: Use JavaScript Standard Style (http://standardjs.com)
          24
2 instances ignored, need to fix:

    ./lib/commands/servo.js:56:67: Expected error to be handled. (handle-callback-err)
    ./lib/commands/servo.js:87:14: Expected error to be handled. (handle-callback-err)
These changes are primarily:

        > standard --fix lib/controllers/project.js

This file was skipped earlier because of issue with `await`. I disabled one line since fixing it requires more than linting:

    ./lib/controllers/project.js:311:74: Expected error to be handled. (handle-callback-err)
disabled regex creation warning, rather than fixing it, since this code
will probably be refactored heavily in coming commits
Copy link
Contributor

@theworkflow theworkflow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Error when running npm test

Error: Cannot find module 'express'
    at Function.Module._resolveFilename (module.js:469:15)
    at Function.Module._load (module.js:417:25)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/Jeremiah/Code/xervo/cli/test/mockServer.js:1:77)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at /Users/Jeremiah/Code/xervo/cli/node_modules/lab/lib/cli.js:104:23
    at Array.forEach (native)
    at Object.internals.traverse (/Users/Jeremiah/Code/xervo/cli/node_modules/lab/lib/cli.js:100:19)
    at Object.exports.run (/Users/Jeremiah/Code/xervo/cli/node_modules/lab/lib/cli.js:49:29)
    at Object.<anonymous> (/Users/Jeremiah/Code/xervo/cli/node_modules/lab/bin/lab:3:23)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.runMain (module.js:604:10)
    at run (bootstrap_node.js:394:7)
    at startup (bootstrap_node.js:149:9)
    at bootstrap_node.js:509:3

@jackboberg
Copy link
Contributor Author

npm test, and the entire unit test setup, deserves some effort...I want to get linting in place so that we can move towards better test coverage

@bsatrom
Copy link
Contributor

bsatrom commented Feb 7, 2017

Everything worked for me 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants