Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduce a severity level for issues, and a 'warning' severity #931
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
Introduce a severity level for issues, and a 'warning' severity #931
Changes from all commits
ff6cf12
e81ce3d
8415b90
11dec4b
6715362
7cdfeb2
ca838a3
04f115f
a51b385
fba703f
cefc62d
f224697
e9c84c3
50a6143
b8f81cf
b74187c
02996d7
ce1f4b8
5b5bfca
c7ff8a2
51c5327
39f8ac6
a101445
d7c8bdc
b64d7a3
8902a96
1e6e866
95d83ff
c23a4d6
9fa497e
57f2221
4811f39
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For now, until we've proposed the change list for ABIv1, I think we should just leave this switch out. It'll be easy to add back in v1 (actually, there's a whole different way we can do it that may be more scalable, I'll discuss with you in DMs.)
I say this because somebody passing
1
here is either from the future or is providing what is currently invalid input.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See also my comment here: https://github.com/swiftlang/swift-testing/pull/931/files#r1944900283
I realize I'm being confusing, sorry.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replied there, and in the mean time we need this so the tests can opt-in.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aren't the tests passing
isWarningIssueRecordedEventEnabled
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This
switch
case doesn't actually enable the feature for ABIv1, it ensures that it remains disabled for ABIv0. We definitely want that safeguard, even if we decide not to enable this feature in ABIv1.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As of right now, it's dead code since the default value is always
false
though.