Skip to content
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

Remove severity #943

Merged
merged 1 commit into from
Mar 20, 2025
Merged

Remove severity #943

merged 1 commit into from
Mar 20, 2025

Conversation

bkolb
Copy link
Contributor

@bkolb bkolb commented Feb 21, 2025

Instead of making the severity configurable,
this patch removes severity all together and treats every finding as an error.

Issue: #879

@bkolb bkolb force-pushed the removeWarnings branch 4 times, most recently from d5307db to 6b359d8 Compare February 24, 2025 12:27
Copy link
Member

@ahoppen ahoppen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, Bernd. Looks good to me overall, just have a few thoughts inline. I would also like to hear @allevato’s opinion before merging this.

@bkolb bkolb force-pushed the removeWarnings branch 2 times, most recently from 382c324 to dec91d5 Compare March 12, 2025 21:32
@bkolb bkolb force-pushed the removeWarnings branch 7 times, most recently from 476b317 to d27a15d Compare March 18, 2025 14:54
@bkolb
Copy link
Contributor Author

bkolb commented Mar 18, 2025

I think I addressed all your comments. Can you please check again?

Copy link
Member

@allevato allevato left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! This is a lot cleaner.

Copy link
Member

@allevato allevato left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like these need to be added to api-breakages.txt:

7 breaking changes detected in SwiftFormat:
  💔 API breakage: func Rule.diagnose(_:on:severity:anchor:notes:) has parameter 2 type change from SwiftFormat.Finding.Severity? to SwiftFormat.FindingAnchor
  💔 API breakage: func Rule.diagnose(_:on:severity:anchor:notes:) has parameter 3 type change from SwiftFormat.FindingAnchor to [SwiftFormat.Finding.Note]
  💔 API breakage: enum Finding.Severity has been removed
  💔 API breakage: var Finding.severity has been removed
  💔 API breakage: var FindingCategorizing.defaultSeverity has been removed
  💔 API breakage: var FindingCategorizing.defaultSeverity has been removed
  💔 API breakage: func Rule.diagnose(_:on:severity:anchor:notes:) has been renamed to func diagnose(_:on:anchor:notes:)

Verified

This commit was signed with the committer’s verified signature.
bkolb Bernd Kolb
Instead of making the severity configurable,
this patch removes severity all together and treats
every finding as an error.

Issue: swiftlang#879
@bkolb
Copy link
Contributor Author

bkolb commented Mar 20, 2025

I updated the api-breakages.txt file. Can you please approve the workflow again?

@allevato allevato merged commit 2aae1e0 into swiftlang:main Mar 20, 2025
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants