Skip to content
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

Issues with console logging and output channels #350

Open
alekdavis opened this issue Jan 8, 2025 · 2 comments
Open

Issues with console logging and output channels #350

alekdavis opened this issue Jan 8, 2025 · 2 comments

Comments

@alekdavis
Copy link

alekdavis commented Jan 8, 2025

In addition to the already reported issue, let me bring a couple of others.

First, the httpyac - Console output seems buggy and not very useful. Even if I clear it before running tests, the old entries still appear after a new run (with the first record messed up):

image

I'm wondering if this is a VSCode bug, but given that the console log entries also appear in the TEST RESULTS window, I'm not even sure what purpose the httpyac - Console output channel serves? I can't think of a case when this would be useful.

Second, the httpyac - Log output channel also shows the old entries (after I cleared them), so I suspect it's a VSCode issue, but another problem is that it seems to group all console log outputs from all tests before the the results section:

image

Not sure what benefit all these bundled log entries would serve, since it would be next to impossible to determine what tests they are tied to. There is some useful info in the httpyac - Log channel, but maybe it would make more sense to not send the console logs there at all to make it cleaner?

I'm using a test script from the link above.

@AnWeber
Copy link
Owner

AnWeber commented Jan 8, 2025

I already created an issue for this: microsoft/vscode#224516

@alekdavis
Copy link
Author

Cool. What about all console log messages in the httpyac - Log output appearing before test logs? Is this a VSCode bug? Or is this behavior intentional?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants