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

Remove "Message:" prefix from the output from Message function (running in VS Code) #1081

Closed
tcNickolas opened this issue Jan 29, 2024 · 2 comments
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@tcNickolas
Copy link
Member

Describe the bug

Prefacing the output from the Message function with "Message:" (when running in VS Code) looks very jarring to me, and not what I expect. It makes sense to call out "Result" explicitly, since this happens once per program, and DumpMachine output is large enough that a "DumpMachine" prefix doesn't stand out, but the "Message" prefix looks noisy.

Screenshots

For example, in the following example I use newlines to add a break between different parts of the example, and having "Message:" strings makes it look odd:

image

System information

  • QDK 1.0.33
@tcNickolas tcNickolas added bug Something isn't working needs triage labels Jan 29, 2024
@swernli swernli added the good first issue Good for newcomers label Jan 30, 2024
@colommar
Copy link
Contributor

Hi, I'd like to clarify the requirements. Is it ideal to remove the message: and directly output the content in the message?

@tcNickolas
Copy link
Member Author

Yes

github-merge-queue bot pushed a commit that referenced this issue Feb 22, 2024
…g the `Message:` (#1175)

## What have been changed
delete the debugger output `Message:`

## Issue mentioned
finish the open issue #1081.

## What will happen
message will directly output the content in the message without typing
the `Message:`
@swernli swernli closed this as completed Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants