Danny Mösch

I'm unable to reproduce this issue. Both examples trigger with version 0.57.1 on my side. With the option `ignore_multiline_statement_conditions` set to `true` there's no violation. Please double check.

It's not a rule but an option of `opening_brace`. See its [documentation](https://realm.github.io/SwiftLint/opening_brace.html).

Adding documentation for the various options of all rules is a long term effort, but definitely desired. At the moment, though, there's no infrastructure prepared to do that.

> > Adding documentation for the various options of all rules is a long term effort, but definitely desired. > > At the moment, though, there's no infrastructure prepared to...

So your point is that you don't just want to ignore braces after multiline conditions but enforce them to be on their own line. Correct?

> > So your point is that you don't just want to ignore braces after multiline conditions but enforce them to be on their own line. Correct? > > Yes,...

To avoid restricting the rule too much by ignoring variable declarations with attributes entirely, we might instead go with a new option that allows to skip variables annotated by any...

As a general rule one should avoid having the include and exclude patterns match too many files. They should be rather specific to avoid performance issues. I hope this restriction...

> Hi @SimplyDanny! My colleague @hyeffie and I are interested in implementing this rule. We're currently working on the additional UIColor magic numbers PR (#6035), but would also like to...

You need to rebase onto `main` first to fix conflicts and build with the latest infrastructure. Ignore the conflict in `GeneratedTests.swift` and let the file be deleted. Eventually, run `swift...