Treat compactMap as standard function

[SimplyDanny]

No description provided.

[SwiftLintBot]

	130 Warnings
⚠️	If this is a user-facing change, please include a CHANGELOG entry to credit yourself! You can find it at CHANGELOG.md.
⚠️	This PR introduced a violation in Brave: /App/ShareExtension/ShareToBraveViewController.swift:73:19: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/Brave/Frontend/Browser/BrowserViewController/BVC+Playlist.swift:70:107: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/Brave/Frontend/Browser/BrowserViewController/BVC+ToolbarDelegate.swift:372:107: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/Brave/Frontend/Browser/BrowserViewController/BrowserViewController.swift:1196:41: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/Brave/Frontend/Browser/BrowserViewController/BrowserViewController.swift:516:48: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/Brave/Frontend/Browser/BrowserViewController/BrowserViewController.swift:550:50: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/Brave/Frontend/Browser/Search/SearchEngines.swift:322:128: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/Brave/Frontend/Browser/TabManager.swift:504:40: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/Brave/Frontend/Browser/Tabs/TabTray/TabTrayController+TableViewDelegate.swift:188:42: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/Brave/Frontend/UserContent/UserScripts/Scripts_Dynamic/ScriptHandlers/Paged/SolanaProviderScriptHandler.swift:308:68: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/Brave/Migration/Migration.swift:77:19: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/Brave/Migration/Migration.swift:83:61: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/BraveNews/Composer/FeedDataSource.swift:843:59: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/BraveWallet/Settings/CustomNetworkDetailsView.swift:141:31: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/BraveWallet/Settings/CustomNetworkDetailsView.swift:165:32: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/BraveWallet/Settings/CustomNetworkDetailsView.swift:189:33: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/Data/models/PlaylistItem.swift:292:36: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/Data/models/PlaylistItem.swift:294:52: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/Playlist/PlaylistManager.swift:233:21: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Sources/Playlist/PlaylistManager.swift:783:67: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Brave: /Tests/ClientTests/SearchEnginesTests.swift:51:60: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in DuckDuckGo: /DuckDuckGo/DaxDialogs.swift:719:25: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in DuckDuckGo: /DuckDuckGo/PrivacyDashboard/PrivacyDashboardViewController.swift:339:88: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in DuckDuckGo: /DuckDuckGo/TabManager.swift:318:55: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /BrowserKit/Sources/TabDataStore/TabSessionStore.swift:76:43: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/Client/Application/WindowManager.swift:112:56: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/Client/Utils/BackgroundTabLoader.swift:46:46: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/Providers/RustSyncManager.swift:570:88: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/Shared/Functions.swift:227:28: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/Redux/PocketStateTests.swift:45:55: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/Redux/TopSitesSectionStateTests.swift:36:57: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/Redux/TopSitesSectionStateTests.swift:56:57: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/TopSitesManagerTests.swift:138:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/TopSitesManagerTests.swift:139:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/TopSitesManagerTests.swift:154:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/TopSitesManagerTests.swift:155:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/TopSitesManagerTests.swift:172:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/TopSitesManagerTests.swift:173:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/TopSitesManagerTests.swift:195:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/TopSitesManagerTests.swift:204:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/TopSitesManagerTests.swift:222:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/TopSitesManagerTests.swift:228:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/TopSitesManagerTests.swift:249:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/TopSitesManagerTests.swift:250:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/TopSitesManagerTests.swift:52:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/TopSitesManagerTests.swift:53:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/TopSitesManagerTests.swift:89:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Firefox: /firefox-ios/firefox-ios-tests/Tests/ClientTests/Frontend/Homepage Rebuild/TopSitesManagerTests.swift:90:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Kickstarter: /KsApi/models/ProjectAndBackingEnvelope.swift:17:19: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Kickstarter: /KsApi/models/ProjectStatsEnvelope.swift:82:18: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Kickstarter: /KsApi/models/graphql/adapters/Project+ProjectFragment.swift:42:76: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Kickstarter: /Library/DataSource/ValueCellDataSourceTests.swift:157:39: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Kickstarter: /Library/DataSource/ValueCellDataSourceTests.swift:158:39: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Kickstarter: /Library/ViewModels/ManagePledgeViewModel.swift:233:21: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Kickstarter: /Library/ViewModels/PledgeExpandableRewardsHeaderViewModel.swift:69:21: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Kickstarter: /Library/ViewModels/PostCampaignPledgeRewardsSummaryViewModel.swift:78:21: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Kickstarter: /Library/ViewModels/ReportProjectFormViewModel.swift:48:19: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Kickstarter: /Library/ViewModels/RewardsCollectionViewModelTests.swift:117:80: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Kickstarter: /Library/ViewModels/RewardsCollectionViewModelTests.swift:158:80: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Kickstarter: /Library/ViewModels/RewardsCollectionViewModelTests.swift:201:80: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Kickstarter: /Library/ViewModels/RewardsCollectionViewModelTests.swift:79:80: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Moya: /Sources/CombineMoya/Publisher+Response.swift:84:25: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Sources/Account/Account.swift:1253:39: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Sources/Account/Account.swift:1344:47: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Sources/Account/Account.swift:1347:51: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Sources/Account/CloudKit/CloudKitAccountZoneDelegate.swift:151:68: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Sources/Account/Feedly/FeedlyAccountDelegate.swift:352:81: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Sources/Account/Feedly/Models/FeedlyEntryParser.swift:76:45: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Sources/Account/NewsBlur/Internals/NewsBlurAccountDelegate+Internal.swift:293:41: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Sources/Account/ReaderAPI/ReaderAPIAccountDelegate.swift:717:55: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Sources/Account/ReaderAPI/ReaderAPIAccountDelegate.swift:734:31: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Sources/Account/ReaderAPI/ReaderAPIAccountDelegate.swift:880:40: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Sources/Account/ReaderAPI/ReaderAPICaller.swift:616:46: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Sources/Account/ReaderAPI/ReaderAPICaller.swift:659:64: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Tests/AccountTests/Feedly/FeedlyEntryParserTests.swift:67:42: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Tests/AccountTests/Feedly/FeedlyEntryParserTests.swift:71:56: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Tests/AccountTests/Feedly/FeedlyMirrorCollectionsAsFoldersOperationTests.swift:140:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Tests/AccountTests/Feedly/FeedlyMirrorCollectionsAsFoldersOperationTests.swift:141:50: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Tests/AccountTests/Feedly/FeedlyMirrorCollectionsAsFoldersOperationTests.swift:50:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Tests/AccountTests/Feedly/FeedlyMirrorCollectionsAsFoldersOperationTests.swift:51:50: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Tests/AccountTests/Feedly/FeedlyMirrorCollectionsAsFoldersOperationTests.swift:93:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Tests/AccountTests/Feedly/FeedlyMirrorCollectionsAsFoldersOperationTests.swift:94:50: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Tests/AccountTests/Feedly/FeedlyTestSupport.swift:109:44: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Account/Tests/AccountTests/Feedly/FeedlyTestSupport.swift:110:42: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /ArticlesDatabase/Sources/ArticlesDatabase/SearchTable.swift:215:42: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /ArticlesDatabase/Sources/ArticlesDatabase/SearchTable.swift:60:38: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in NetNewsWire: /Mac/MainWindow/Timeline/TimelineViewController.swift:272:91: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in PocketCasts: /Modules/Server/Sources/PocketCastsServer/Public/Sync/SyncTask.swift:88:75: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in PocketCasts: /podcasts/SharePublishViewController.swift:112:54: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Realm: /Realm/ObjectServerTests/RealmServer.swift:1192:57: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Sourcery: /Sourcery/Sourcery.swift:439:25: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Sourcery: /SourceryRuntime/Sources/Common/Composer/ParserResultsComposed.swift:571:68: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Sourcery: /SourceryTests/Output/DryOutputSpec.swift:496:71: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Wire: /wire-ios-data-model/Source/Model/Message/ZMClientMessage+Encryption.swift:244:58: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in Wire: /wire-ios-mocktransport/Source/Clients and OTR/MockTransportSession+OTR.swift:169:76: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/Stores/ActivityStore.swift:153:25: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/Stores/ActivityStore.swift:169:25: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/Stores/PluginStore.swift:239:25: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/Stores/PluginStore.swift:246:25: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/Stores/PluginStore.swift:268:25: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/ViewRelated/Jetpack/Jetpack Scan/JetpackScanCoordinator.swift:46:63: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/ViewRelated/Stats/Charts/PeriodChart.swift:79:49: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/ViewRelated/Stats/Charts/PeriodChart.swift:80:52: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/ViewRelated/Stats/Charts/PeriodChart.swift:81:49: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/ViewRelated/Stats/Charts/PeriodChart.swift:82:52: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/ViewRelated/Stats/Charts/PostChart.swift:100:42: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/ViewRelated/Stats/Insights/InsightType.swift:54:33: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/ViewRelated/Stats/Insights/SiteStatsInsightsTableViewController.swift:112:92: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/ViewRelated/Stats/Insights/SiteStatsInsightsTableViewController.swift:620:48: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/ViewRelated/Stats/Insights/SiteStatsInsightsViewModel.swift:454:64: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/ViewRelated/Stats/Insights/SiteStatsInsightsViewModel.swift:456:64: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/ViewRelated/Stats/Insights/SiteStatsInsightsViewModel.swift:458:64: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/ViewRelated/Stats/Insights/SiteStatsInsightsViewModel.swift:460:64: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/ViewRelated/Stats/Insights/SiteStatsInsightsViewModel.swift:465:65: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/ViewRelated/Stats/Insights/SiteStatsInsightsViewModel.swift:467:65: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/ViewRelated/Stats/Insights/SiteStatsInsightsViewModel.swift:469:65: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/Classes/ViewRelated/Stats/Insights/SiteStatsInsightsViewModel.swift:471:65: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/WordPressShareExtension/ShareExtractor.swift:175:59: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/WordPressShareExtension/ShareExtractor.swift:176:65: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	This PR introduced a violation in WordPress: /WordPress/WordPressShareExtension/ShareExtractor.swift:177:66: warning: Prefer Key Path Violation: Use a key path argument instead of a closure with property access (prefer_key_path)
⚠️	Danger found 130 violations with this PR. Due to GitHub's max issue comment size, the number shown has been truncated to 121.

	17 Messages
📖	Linting Aerial with this PR took 0.16s vs 0.16s on main (0% slower)
📖	Linting Alamofire with this PR took 0.16s vs 0.17s on main (5% faster)
📖	Linting Brave with this PR took 0.63s vs 0.61s on main (3% slower)
📖	Linting DuckDuckGo with this PR took 0.49s vs 0.49s on main (0% slower)
📖	Linting Firefox with this PR took 1.43s vs 1.4s on main (2% slower)
📖	Linting Kickstarter with this PR took 0.75s vs 0.75s on main (0% slower)
📖	Linting Moya with this PR took 0.12s vs 0.14s on main (14% faster)
📖	Linting NetNewsWire with this PR took 0.3s vs 0.3s on main (0% slower)
📖	Linting Nimble with this PR took 0.15s vs 0.15s on main (0% slower)
📖	Linting PocketCasts with this PR took 0.69s vs 0.71s on main (2% faster)
📖	Linting Quick with this PR took 0.12s vs 0.12s on main (0% slower)
📖	Linting Realm with this PR took 0.42s vs 0.41s on main (2% slower)
📖	Linting Sourcery with this PR took 0.27s vs 0.27s on main (0% slower)
📖	Linting Swift with this PR took 0.41s vs 0.4s on main (2% slower)
📖	Linting VLC with this PR took 0.2s vs 0.19s on main (5% slower)
📖	Linting Wire with this PR took 1.69s vs 1.66s on main (1% slower)
📖	Linting WordPress with this PR took 1.07s vs 1.04s on main (2% slower)

Here's an example of your CHANGELOG entry:

* Treat `compactMap` as standard function.  
  [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 🚫 Danger