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 DiagnosticLogEntryProduced event. #3003

Merged
merged 1 commit into from
May 30, 2023

Conversation

shyamnamboodiripad
Copy link
Contributor

No description provided.

@@ -69,7 +69,7 @@ public KernelCommandAndEventReceiver(ReadCommandOrEvent readCommandOrEvent)
{
Log.Error(exception);

return new CommandOrEvent(new DiagnosticLogEntryProduced(exception.Message, KernelCommand.None), true);
return new CommandOrEvent(new ErrorProduced(exception.Message, KernelCommand.None), isParseError: true);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not entirely sure if using ErrorProduced for this is ok. I was not able to figure out another way to handle this (other than allowing the exception to propagate). Please let me know in case you think this is not ok.

@shyamnamboodiripad shyamnamboodiripad force-pushed the remove-diagnostic-log branch 2 times, most recently from f1ba8fe to dbe258f Compare May 26, 2023 23:55
@colombod
Copy link
Member

Why deleting this? The original goal for this event was to be intercepted by the vscode extension and routed tot he diagnostics and logs outputs.

@shyamnamboodiripad
Copy link
Contributor Author

Why deleting this? The original goal for this event was to be intercepted by the vscode extension and routed tot he diagnostics and logs outputs.

Ah this was something that @jonsequitur and I had discussed. We already removed the #!log magic command in an earlier change - this event seemed like a vestige that is no longer useful.

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

Successfully merging this pull request may close these issues.

2 participants