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

Add baseline switch to nyc instrument command #1261

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

AndrewFinlay
Copy link
Contributor

@AndrewFinlay AndrewFinlay commented Jan 2, 2020

This implements #1202

Adds the switch --baseline that creates a baseline coverage file when running nyc instrument ....
The baseline coverage files is saved to <temp-dir>/baseline/coverage.json.
The baseline coverage file saves the zero coverage state for all files specified by your configuration.
Include this file when reporting to highlight source files with no coverage.

Note that <temp-dir>/baseline/coverage.json isn't automatically included when running nyc report.
However this might not be such an issue when running nyc for instrumentation and reporting only.

Adds the switch `--baseline` that creates a baseline coverage file when running `nyc instrument ...`.
The baseline coverage files is saved to `<temp-dir>/baseline/coverage.json`.
The baseline coverage file saves the zero coverage state for all files specified by your configuration.
Include this file when reporting to highlight source files with no coverage.

Note that  `<temp-dir>/baseline/coverage.json` isn't automatically included when running `nyc report`.
However this might not be such an issue when running nyc for instrumentation and reporting only.
@stale
Copy link

stale bot commented Jan 10, 2021

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label Jan 10, 2021
@AndrewFinlay
Copy link
Contributor Author

bump. Still relevant, from memory this needs work to finish.

@stale stale bot removed the stale label Jan 12, 2021
@stale
Copy link

stale bot commented Apr 16, 2022

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label Apr 16, 2022
@AndrewFinlay
Copy link
Contributor Author

bump, Still relevant, I'll take another look when there's some maintainer interest

@stale stale bot removed the stale label Apr 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant