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
Add option to write diagnostics to a file to provide more information to tools (#494)
* Deprecate using diagnostics as errors.
The error formatting is implicitly tied to a specific diagnostic writer
The diagnostics include more information that gets lost when they are
raised as errors.
* Update calls to deprecated diagnostic-as-error properties
* Add "features.json" to indicate feature availability to other tools
* Add diagnostic consumer that writes to a file
rdar://105181169
* Update calls to deprecated diagnostic properties
* Fix bug in preview test where some diagnostics were written twice
* Fix issue where preview tests would assert if one encountered an error
* Separate formatting of diagnostics for tools and for people
* Rename 'formattedDescriptionFor(...)' to 'formattedDescription(...)'
* Add tests for DiagnosticFileWriter
* Use SemanticVersion type for DiagnosticFile version
* Use dedicated diagnostic file severity type
* Rename 'formattedDescription(_:)' to 'formattedDescription(for:)'
* Document DiagnosticFileWriter API
* Correct install location of features.json file
* Correct install location of features.json file
/// Creates a new instance of this class with the provided output stream and filter level.
22
23
/// - Parameter stream: The output stream to which this instance will write.
23
24
/// - Parameter filterLevel: Determines what diagnostics should be printed. This filter level is inclusive, i.e. if a level of ``DiagnosticSeverity/information`` is specified, diagnostics with a severity up to and including `.information` will be printed.
0 commit comments