SwiftLintBot
commented
6 months ago | 1 Warning | |
|---|---|
| :warning: | If this is a user-facing change, please include a CHANGELOG entry to credit yourself! You can find it at CHANGELOG.md. |
| 17 Messages | |
|---|---|
| :book: | Linting Aerial with this PR took 1.28s vs 1.23s on main (4% slower) |
| :book: | Linting Alamofire with this PR took 1.8s vs 1.79s on main (0% slower) |
| :book: | Linting Brave with this PR took 10.44s vs 10.35s on main (0% slower) |
| :book: | Linting DuckDuckGo with this PR took 5.52s vs 5.51s on main (0% slower) |
| :book: | Linting Firefox with this PR took 12.85s vs 12.79s on main (0% slower) |
| :book: | Linting Kickstarter with this PR took 12.53s vs 12.4s on main (1% slower) |
| :book: | Linting Moya with this PR took 0.69s vs 0.68s on main (1% slower) |
| :book: | Linting NetNewsWire with this PR took 3.7s vs 3.7s on main (0% slower) |
| :book: | Linting Nimble with this PR took 1.02s vs 1.01s on main (0% slower) |
| :book: | Linting PocketCasts with this PR took 10.18s vs 10.15s on main (0% slower) |
| :book: | Linting Quick with this PR took 0.45s vs 0.44s on main (2% slower) |
| :book: | Linting Realm with this PR took 6.3s vs 6.36s on main (0% faster) |
| :book: | Linting Sourcery with this PR took 3.12s vs 3.11s on main (0% slower) |
| :book: | Linting Swift with this PR took 6.24s vs 6.18s on main (0% slower) |
| :book: | Linting VLC with this PR took 1.67s vs 1.66s on main (0% slower) |
| :book: | Linting Wire with this PR took 23.46s vs 23.27s on main (0% slower) |
| :book: | Linting WordPress with this PR took 15.34s vs 15.15s on main (1% slower) |
Here's an example of your CHANGELOG entry:
* Report specific issues.
[SimplyDanny](https://github.com/SimplyDanny)
[#issue_number](https://github.com/realm/SwiftLint/issues/issue_number)note: There are two invisible spaces after the entry's text.
Generated by :no_entry_sign: Danger
Use different issues to make inlineable configurations work in both scenarios, namely being used standalone and nested as part of another configuration. In the latter case, finding no values to parse in a raw configuration is okay, while as a standalone configuration it's not.