Danny Mösch

I would highly appreciate if you could take a look on this again, @marcelofabri. Other changes are causing regular merge conflicts in this huge PR. There is room for more...

Would you mind taking a look into this PR, @jpsim? I would like to continue with some more improvements to the documentation of rule configurations. If we agree on the...

First of all: Thank you for the contribution and sorry for the late feedback! I like the idea of supporting patterns for excluded names. However, the `NameConfiguration` already contains a...

There is no way for the rule to know the types of the operands. Only the special Analyzer rules know. Thus, this is a false-positive we have to accept or...

There already is [one rule](https://realm.github.io/SwiftLint/accessibility_label_for_image.html) available and [another one](https://github.com/realm/SwiftLint/pull/3989) in the works referring to SwiftUI. Do you have ideas for specific rules? Please file rule requests for them.

The rule has been disabled generally in extensions since it is not possible to know whether an extension is for a struct or a class or an enum in the...

It works for me. I run `swiftlint lint --config ../.swiftlint.yml` in a directory with one Swift file while the configuration is located in the parent directory. Disabling/enabling specific rules in...

Sorry for the late response! Could you please rebase your branch? Notice that the protocol `AutomaticTestableRule` has been removed. All rules are now automatically tested. The file `AutomaticRuleTests.generated.swift` has been...

As long as this enhancement is not implemented I recommend enabling rules one after another using the `only_rules` list in the configuration. Activate a new rule, agree on it, fix...

I think enough advice has been provided. Closing the issue for now.