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
Include severity and isFailure for Issues in the published JSON event stream (#1279)
### Motivation:
- Proposed and accepted in ST-0013 [^1], so we can move ahead and
include this in the event stream.
- This will _not_ be available in event stream version 0 as this is
considered a breaking change [^2]
### Modifications:
- Promote existing _severity/_isFailure fields -> severity/isFailure
without the underscores
This effectively makes them part of the official JSON ABI. The
underscored names will no longer be accessible, but they were always
experimental so this is not considered a blocker.
- Only emit severity/isFailure when using event stream version >= 6.3
This removes access to the underscored names from earlier versions, but
again, these were experimental.
- Remove hidden `__CommandLineArguments_v0` argument
`isWarningIssueRecordedEventEnabled`
This was only for internal testing use, but is obsolete because we test
issue severity by specifying event stream version >= 6.3.
### Checklist:
- [x] Code and documentation should follow the style of the [Style
Guide](https://github.com/apple/swift-testing/blob/main/Documentation/StyleGuide.md).
- [x] If public symbols are renamed or modified, DocC references should
be updated.
[^1]:
https://github.com/swiftlang/swift-evolution/blob/main/proposals/testing/0013-issue-severity-warning.md
[^2]:
https://github.com/swiftlang/swift-evolution/blob/main/proposals/testing/0013-issue-severity-warning.md#integration-with-supporting-tools
Fixes rdar://158621033
0 commit comments