-
-
Notifications
You must be signed in to change notification settings - Fork 359
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
docs(readme): move advanced features to docs site #551
Conversation
@@ -354,7 +315,7 @@ integrated with coveralls and travis-ci.org: | |||
```json | |||
{ | |||
"script": { | |||
"test": "nyc tap ./test/*.js", | |||
"test": "nyc mocha", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made this change because tap
uses nyc
under the hood for coverage, so it doesn't make sense to go this way. Most of our tutorials use mocha
so I thought I'd just continue that trend.
"report-dir": "./alternative" | ||
} | ||
} | ||
``` | ||
|
||
**.nycrc:** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed this section on the .nycrc
example because it might cause confusion with the package.json
example right above it. I'm hoping that the explanation above that the configuration can be set in either the package.json
or .nycrc
file is enough explanation.
README.md
Outdated
@@ -337,6 +294,10 @@ You can specify custom high and low watermarks in nyc's configuration: | |||
} | |||
``` | |||
|
|||
## Other advanced features | |||
|
|||
Take a look at http://istanbul.js.org/docs/advanced/ and please feel free to contribute documentation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely open to improving this copy.
Depends on istanbuljs/istanbuljs.github.io#37
I did this for the sake of paring down the README to a simpler quick start because I'm finding myself answering the same questions in our issues multiple times. This is just a step towards that end, and a further iteration will see the README better organized somehow [very open to suggestions on this].