You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suggest we style printed text the same way the Console API does rather than using ANSI escape codes across the codebase. In the terminal, styling should look the same. However, the advantage is that escape codes are omitted in places where raw characters aren't handled in special ways. E.g., text files. The differences can be seen here.
This behavior is especially cumbersome in scenarios where analyzing output is important. For example, deno test output is printed in the terminal in CI. When advanced troubleshooting is required, a user will download the logs but must deal with the clutter generated from ANSI escape codes.
Disclaimer: I'm unfamiliar with the Console API's inner workings, including how it applies styling to printed output.
I suggest we style printed text the same way the Console API does rather than using ANSI escape codes across the codebase. In the terminal, styling should look the same. However, the advantage is that escape codes are omitted in places where raw characters aren't handled in special ways. E.g., text files. The differences can be seen here.
produces
output.txt
:and
produces
output.txt
:This behavior is especially cumbersome in scenarios where analyzing output is important. For example,
deno test
output is printed in the terminal in CI. When advanced troubleshooting is required, a user will download the logs but must deal with the clutter generated from ANSI escape codes.Disclaimer: I'm unfamiliar with the Console API's inner workings, including how it applies styling to printed output.
Related #23316
The text was updated successfully, but these errors were encountered: