SwiftLintBot
commented
3 months ago | 17 Messages | |
|---|---|
| :book: | Linting Aerial with this PR took 1.13s vs 1.12s on main (0% slower) |
| :book: | Linting Alamofire with this PR took 1.63s vs 1.65s on main (1% faster) |
| :book: | Linting Brave with this PR took 9.43s vs 9.5s on main (0% faster) |
| :book: | Linting DuckDuckGo with this PR took 5.03s vs 5.0s on main (0% slower) |
| :book: | Linting Firefox with this PR took 11.56s vs 11.84s on main (2% faster) |
| :book: | Linting Kickstarter with this PR took 11.34s vs 11.37s on main (0% faster) |
| :book: | Linting Moya with this PR took 0.63s vs 0.64s on main (1% faster) |
| :book: | Linting NetNewsWire with this PR took 3.35s vs 3.33s on main (0% slower) |
| :book: | Linting Nimble with this PR took 0.93s vs 0.93s on main (0% slower) |
| :book: | Linting PocketCasts with this PR took 9.15s vs 9.16s on main (0% faster) |
| :book: | Linting Quick with this PR took 0.42s vs 0.43s on main (2% faster) |
| :book: | Linting Realm with this PR took 5.76s vs 5.79s on main (0% faster) |
| :book: | Linting Sourcery with this PR took 2.82s vs 2.88s on main (2% faster) |
| :book: | Linting Swift with this PR took 5.57s vs 5.61s on main (0% faster) |
| :book: | Linting VLC with this PR took 1.53s vs 1.54s on main (0% faster) |
| :book: | Linting Wire with this PR took 20.84s vs 21.21s on main (1% faster) |
| :book: | Linting WordPress with this PR took 13.69s vs 13.81s on main (0% faster) |
Generated by :no_entry_sign: Danger
The README states that a configuration like
attributes: erroris valid to only set a different severity level for a rule (theattributesrule here). This was previously only possible for rules that were accompanied by a plain severity configuration.I don't think this broke with the automatic parsing code generation. For some rules it might have worked before, for others not. This change makes it consistently working for all rules.