SwiftLintBot
commented
3 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 0.8s vs 0.8s on main (0% slower) |
| :book: | Linting Alamofire with this PR took 1.15s vs 1.14s on main (0% slower) |
| :book: | Linting Brave with this PR took 6.53s vs 6.66s on main (1% faster) |
| :book: | Linting DuckDuckGo with this PR took 3.5s vs 3.6s on main (2% faster) |
| :book: | Linting Firefox with this PR took 9.0s vs 9.05s on main (0% faster) |
| :book: | Linting Kickstarter with this PR took 8.06s vs 8.27s on main (2% faster) |
| :book: | Linting Moya with this PR took 0.48s vs 0.46s on main (4% slower) |
| :book: | Linting NetNewsWire with this PR took 2.33s vs 2.37s on main (1% faster) |
| :book: | Linting Nimble with this PR took 0.67s vs 0.69s on main (2% faster) |
| :book: | Linting PocketCasts with this PR took 7.06s vs 7.05s on main (0% slower) |
| :book: | Linting Quick with this PR took 0.32s vs 0.32s on main (0% slower) |
| :book: | Linting Realm with this PR took 4.23s vs 4.16s on main (1% slower) |
| :book: | Linting Sourcery with this PR took 1.99s vs 2.02s on main (1% faster) |
| :book: | Linting Swift with this PR took 3.81s vs 3.88s on main (1% faster) |
| :book: | Linting VLC with this PR took 1.08s vs 1.09s on main (0% faster) |
| :book: | Linting Wire with this PR took 14.25s vs 14.48s on main (1% faster) |
| :book: | Linting WordPress with this PR took 9.39s vs 9.3s on main (0% slower) |
Here's an example of your CHANGELOG entry:
* Allow to infer option names.
[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
This allows to infer names of options from their names in a configuration. CamelCase is translated into snake_case automatically when
applyis triggered.RuleConfigurations conform toInlinableOptionType. Mark types that must have this capability explicitly. Same forAcceptableByConfigurationElement.InlinableOptionTypedoesn't mean it's automatically inlined. This also doesn't depend on the fact of having a name for its key configured any longer. Instead, aninlineattribute must explicitly be set totruein@ConfigurationElement.applywhen they are really sure that something is odd. Otherwise, they accept to not being updated.