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
MSBuildWorkspace.WorkspaceFailed reports WorkspaceDiagnosticKind.Failure even for issues that can be safely ignored, such as failure to load project of unregistered extension.
Internally, DiagnosticReporter.Report conflates logging with exception handling. It's unclear why DiagnosticReportingMode is needed.
Callers that pass DiagnosticReportingMode.Throw should just throw the exception directly.
Callers that pass DiagnosticReportingMode.Ignore should not call the method at all - it's a no op.
MSBuildWorkspace.WorkspaceFailed should be called with WorkspaceDiagnosticKind.Failure only for unrecoverable errors. Presumably, we wouldn't immediately throw in these cases so that we can report all the errors. Failure should be reported if and only if the operation fails. If the operation can succeed (e.g. by ignoring certain projects) a warning should be reported.
MSBuildWorkspace.WorkspaceFailed
reportsWorkspaceDiagnosticKind.Failure
even for issues that can be safely ignored, such as failure to load project of unregistered extension.Internally,
DiagnosticReporter.Report
conflates logging with exception handling. It's unclear whyDiagnosticReportingMode
is needed.Callers that pass
DiagnosticReportingMode.Throw
should just throw the exception directly.Callers that pass
DiagnosticReportingMode.Ignore
should not call the method at all - it's a no op.MSBuildWorkspace.WorkspaceFailed
should be called withWorkspaceDiagnosticKind.Failure
only for unrecoverable errors. Presumably, we wouldn't immediately throw in these cases so that we can report all the errors. Failure should be reported if and only if the operation fails. If the operation can succeed (e.g. by ignoring certain projects) a warning should be reported.Update dotnet-watch once fixed - see dotnet/sdk#43571.
The text was updated successfully, but these errors were encountered: