Danny Mösch

Thanks for the clarification, @tomaskraina! The issue has meanwhile been resolved by #6109.

This is a known issue that #5157 tries to address. It manifests when wildcards used in the `excluded` list resolve to a lot of files. Changes in this area caused...

Thanks for playing around with the fix! > Looks like the `exclude:` part of custom rules is not used in the fix. Yes, it's not part of the fix but...

SwiftLint works on the syntax level only. So it doesn't know which declarations exactly stem from a protocol or parent class. This is why `excludes_inherited_types` exists and, with it enabled,...

Browsing through the Git history I cannot believe a value like `SwiftLintFramework.FileType.mainType` has ever worked. 😅 Also, that you now suddenly see more warnings doesn't really make sense. Can you...

This issue has been marked as stale because it has not seen any activity in the last 4 months. It is going to be closed soon if it stays inactive.

I tried ```swift @MainActor func f() { MainActor.assertIsolated("Not running on main actor") print("Running on main actor") } await f() ``` and it worked. Removing `@MainActor` and adding `async` to `f`...

I don't get it. Where do you want to import what from where?

Sonar itself offers a Swift plugin that can import SwiftLint reports in JSON format. That's what the `sonarqube` reporter generates. The Backelite plugin seems to parse the default SwiftLint output...

Analysis of duplicated code is not part of SwiftLint. It might only be part of the Sonar plugins and I've never used any of them. Therefore, I cannot help you...