clean up debug log as it's too much noise #919
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thafryer
approved these changes
Feb 9, 2024
ethriel3695
added
release
|
🚀 PR was released in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The trace output in the debug logs results in too much noise and is not helpful.
I want to remove the log for the traced file so the debug log is functional again.
I ran this command
yarn chromatic trace -m expanded node-src/ui/components/activity.tsto verify thetraceChangedlogic doesn't throw any errors.I also ran this command without
-m expandedand confirmed the trace logs no longer appear.📦 Published PR as canary version:
10.9.4--canary.919.7845957579.0✨ Test out this PR locally via:
npm install chromatic@10.9.4--canary.919.7845957579.0 # or yarn add chromatic@10.9.4--canary.919.7845957579.0