-
Notifications
You must be signed in to change notification settings - Fork 176
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
The new underlining feature from #191 is a breaking change #203
Comments
Ah, I see that I should use |
Ah, no, I need to re-open this. I want the fancy formatting in terms of error messages, etc. But I definitely do not want object dumps to be processed as "fancy". |
Hmm...this also causes issues with something as simple as I would definitely prefer an opt-in to any delimiter-based options on a per-message basis. Otherwise, any dynamic content could cause a mess on output. |
@pi0 No worries, appreciate both the awesome tool and rapid response :-D. FWIW, I do like the concept that was introduced, I just think that it needs to be selectively opt-in. |
No worries. Can you please test with latest version? Is it still problematic for you? |
@pi0 Good to go! Appreciate the quick turnaround. |
Environment
All
Reproduction
3.1.0 Output
3.2.0 Output
Describe the bug
The console output from 3.2.0 does not match the output from 3.1.0.
Ideally, fancy formatting would be opt-in instead of opt-out at runtime.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: