We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I don't think adding diagnostic info as "notice" is helpful. It would cause a reduction in the use of diagnostics, which can be helpful.
This is likely related to #109.
The text was updated successfully, but these errors were encountered:
@mcollina you would have preferred to only see these in the stdout/spec/tap reporter?
Sorry, something went wrong.
yes exactly
@mcollina I have released a new version to npm, can you check if the latest changes make more sense and if you still feel this is needed?
I would still prefer not to see them, but maybe put it behind an env? I can see folks using this.
No branches or pull requests
I don't think adding diagnostic info as "notice" is helpful. It would cause a reduction in the use of diagnostics, which can be helpful.
This is likely related to #109.
The text was updated successfully, but these errors were encountered: