-
Notifications
You must be signed in to change notification settings - Fork 159
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
fix: use stdout instead of stderr for simple logs in build-docs #1825
Conversation
🦋 Changeset detectedLatest commit: 94d6fd0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Seems like a good idea 🧠 ! Thanks @pv-g |
@pv-g could you update the failing snapshots? ( |
Sure @tatomyr. Just did it. |
those are noisy & annoying otherwise, and just not errors anyway
Co-authored-by: Heather Cloward <[email protected]>
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.
Thank you @pv-g for the contribution!
Hey there,
Using CLI
redocly build-docs
This always prints the following into
stderr
.I have many other stuff happening in my project, and generating multiple docs, so this just adds noise & annoyance, whereas it's just (verbose) logs and not errors anyway.