Skip to content

Commit fbc3bbf

Browse files
authored
Mark Issue.Severity cases with availability. (#1410)
It is necessary to explicitly mark the cases of this enum with their Swift 6.3 availability as it is not inherited when rendered in DocC. ### 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 parent c9e74ad commit fbc3bbf

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

Sources/Testing/Issues/Issue.swift

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,12 +94,20 @@ public struct Issue: Sendable {
9494
///
9595
/// An issue with warning severity does not cause the test it's associated
9696
/// with to be marked as a failure, but is noted in the results.
97+
///
98+
/// @Metadata {
99+
/// @Available(Swift, introduced: 6.3)
100+
/// }
97101
case warning
98102

99103
/// The severity level for an issue which represents an error in a test.
100104
///
101105
/// An issue with error severity causes the test it's associated with to be
102106
/// marked as a failure.
107+
///
108+
/// @Metadata {
109+
/// @Available(Swift, introduced: 6.3)
110+
/// }
103111
case error
104112
}
105113

0 commit comments

Comments
 (0)