fix(attributes): apply arguments-on-new-line to types and functions

[leno23]

Summary

• When attributes_with_arguments_always_on_line_above is enabled (default), functions and types now follow the same rule as variables and imports: attributes without arguments may appear on the same line, while attributes with arguments must be on a separate line.
• Improves violation messaging for misplaced attributes that include arguments.

Fixes #5011

Test plan

• Added non-triggering examples for @objc(Foo) / @objc on classes and functions
• Added triggering examples for @objc(Foo) on the same line as declarations
• CI (Buildkite)

Made with Cursor

[SwiftLintBot]

	17278 Warnings
⚠️	This PR introduced a violation in Aerial: /Aerial/App/AppDelegate.swift:12:1: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Aerial: /Aerial/Source/Models/Cache/VideoManager.swift:72:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Aerial: /Aerial/Source/Models/Downloads/DownloadManager.swift:42:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Protected.swift:114:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Example/Source/AppDelegate.swift:28:1: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Session.swift:521:27: Warning: Attributes with arguments or inside always_on_line_above must be on a new line instead of the same line (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Session.swift:541:27: Warning: Attributes with arguments or inside always_on_line_above must be on a new line instead of the same line (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Session.swift:572:27: Warning: Attributes with arguments or inside always_on_line_above must be on a new line instead of the same line (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DownloadRequest.swift:227:21: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DownloadRequest.swift:239:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DownloadRequest.swift:256:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DownloadRequest.swift:313:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DownloadRequest.swift:346:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DownloadRequest.swift:454:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DownloadRequest.swift:473:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DownloadRequest.swift:489:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DownloadRequest.swift:509:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DownloadRequest.swift:538:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DownloadRequest.swift:570:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DownloadRequest.swift:601:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DataStreamRequest.swift:203:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DataStreamRequest.swift:261:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DataStreamRequest.swift:282:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DataStreamRequest.swift:348:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DataStreamRequest.swift:377:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DataStreamRequest.swift:421:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DataStreamRequest.swift:474:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/WebSocketRequest.swift:35:31: Warning: Attributes with arguments or inside always_on_line_above must be on a new line instead of the same line (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/WebSocketRequest.swift:230:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/WebSocketRequest.swift:256:21: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/WebSocketRequest.swift:279:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/WebSocketRequest.swift:377:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/WebSocketRequest.swift:406:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/WebSocketRequest.swift:417:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/WebSocketRequest.swift:430:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/WebSocketRequest.swift:452:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/WebSocketRequest.swift:485:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DataRequest.swift:144:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DataRequest.swift:178:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DataRequest.swift:199:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DataRequest.swift:220:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DataRequest.swift:322:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DataRequest.swift:339:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DataRequest.swift:359:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DataRequest.swift:386:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DataRequest.swift:416:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/DataRequest.swift:445:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/RequestInterceptor.swift:59:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/RequestInterceptor.swift:123:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/RequestInterceptor.swift:128:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/RequestInterceptor.swift:158:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/RequestInterceptor.swift:163:10: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/RequestInterceptor.swift:168:10: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/RequestInterceptor.swift:179:19: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/RequestInterceptor.swift:194:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/RequestInterceptor.swift:199:10: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/RequestInterceptor.swift:213:19: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/RequestInterceptor.swift:261:10: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/RequestInterceptor.swift:286:10: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/RequestInterceptor.swift:311:10: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/RequestInterceptor.swift:349:19: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/RequestInterceptor.swift:359:19: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/RequestInterceptor.swift:371:19: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/NetworkReachabilityManager.swift:172:10: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Request.swift:714:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Request.swift:747:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Request.swift:768:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Request.swift:804:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Request.swift:816:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Request.swift:833:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Request.swift:850:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Request.swift:867:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Request.swift:887:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Request.swift:909:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Request.swift:931:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Request.swift:948:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Request.swift:973:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Request.swift:993:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Request.swift:1021:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Request.swift:1048:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Core/Request.swift:1077:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/Concurrency.swift:200:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/Concurrency.swift:225:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/Concurrency.swift:724:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/Concurrency.swift:747:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/Concurrency.swift:768:25: Warning: Attributes with arguments or inside always_on_line_above must be on a new line instead of the same line (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/Validation.swift:160:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/Validation.swift:175:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/Validation.swift:188:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/Validation.swift:210:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/Validation.swift:225:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/Validation.swift:238:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/Validation.swift:265:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/Validation.swift:280:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/Validation.swift:302:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/Combine.swift:202:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Source/Features/Combine.swift:587:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/RequestModifierTests.swift:32:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/RequestModifierTests.swift:50:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/RequestModifierTests.swift:73:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/RequestModifierTests.swift:93:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/RequestModifierTests.swift:119:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/RequestModifierTests.swift:138:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/RequestModifierTests.swift:161:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/RequestModifierTests.swift:184:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/CacheTests.swift:139:13: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/CacheTests.swift:160:13: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/CacheTests.swift:225:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/CacheTests.swift:237:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/CacheTests.swift:249:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/CacheTests.swift:261:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/SessionDelegateTests.swift:33:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/SessionDelegateTests.swift:62:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/SessionDelegateTests.swift:88:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/SessionDelegateTests.swift:119:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/SessionDelegateTests.swift:174:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/InternalRequestTests.swift:30:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:31:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:53:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:84:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:105:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:135:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:158:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:190:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:215:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:282:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:323:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:370:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:404:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:434:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:439:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:444:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:477:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:517:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:550:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:591:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:617:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	This PR introduced a violation in Alamofire: /Tests/UploadTests.swift:668:5: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	Danger found 17278 violations with this PR. Due to GitHub's max issue comment size, the number shown has been truncated to 138.

	6825 Messages
📖	Building this branch resulted in the same binary size as when built on main.
📖	Linting Aerial with this PR took 0.83 s vs 0.8 s on main (3% slower).
📖	Linting Alamofire with this PR took 1.13 s vs 1.12 s on main (0% slower).
📖	Linting Brave with this PR took 7.45 s vs 7.46 s on main (0% faster).
📖	Linting DuckDuckGo with this PR took 29.92 s vs 29.96 s on main (0% faster).
📖	Linting Firefox with this PR took 12.73 s vs 12.73 s on main (0% slower).
📖	Linting Kickstarter with this PR took 8.68 s vs 8.68 s on main (0% slower).
📖	Linting Moya with this PR took 0.43 s vs 0.46 s on main (6% faster).
📖	Linting NetNewsWire with this PR took 2.91 s vs 2.89 s on main (0% slower).
📖	Linting Nimble with this PR took 0.69 s vs 0.68 s on main (1% slower).
📖	Linting PocketCasts with this PR took 8.27 s vs 8.4 s on main (1% faster).
📖	Linting Quick with this PR took 0.43 s vs 0.44 s on main (2% faster).
📖	Linting Realm with this PR took 3.01 s vs 3.03 s on main (0% faster).
📖	Linting Sourcery with this PR took 1.92 s vs 1.9 s on main (1% slower).
📖	Linting Swift with this PR took 4.81 s vs 4.82 s on main (0% faster).
📖	Linting SwiftLintPerformanceTests with this PR took 0.34 s vs 0.36 s on main (5% faster).
📖	Linting VLC with this PR took 1.28 s vs 1.28 s on main (0% slower).
📖	Linting Wire with this PR took 19.39 s vs 19.37 s on main (0% slower).
📖	Linting WordPress with this PR took 13.06 s vs 13.06 s on main (0% slower).
📖	This PR fixed a violation in Aerial: /Resources/MainUI/PanelWindowController.swift:11:7: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Resources/MainUI/Settings panels/SourcesViewController.swift:174:11: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Resources/MainUI/VideosViewController.swift:87:11: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Models/Music/Music.swift:60:11: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Models/Music/Music.swift:78:11: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Models/Prefs/PrefsInfo.swift:584:18: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Models/Prefs/PrefsInfo.swift:684:18: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Models/Downloads/AsynchronousOperation.swift:29:19: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Views/AerialView+Player.swift:103:11: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Views/AerialView+Player.swift:108:11: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Views/AerialView+Player.swift:112:11: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Views/AerialView+Player.swift:116:11: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Views/PrefPanel/CheckCellView.swift:41:11: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Views/MainUI/VideoCellView.swift:41:19: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Views/Sources/CheckboxCellView.swift:35:19: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Views/Sources/DescriptionCellView.swift:50:19: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Views/AerialView.swift:659:11: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Views/AerialView.swift:666:11: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Views/AerialView.swift:684:11: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Views/AerialView.swift:693:11: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Views/AerialView.swift:724:11: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Views/AerialView.swift:737:11: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Views/AerialView.swift:742:11: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Views/AerialView.swift:753:11: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Aerial: /Aerial/Source/Views/AerialView.swift:762:11: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Alamofire: /Source/Core/WebSocketRequest.swift:35:31: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Alamofire: /Source/Core/Session.swift:521:27: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Alamofire: /Source/Core/Session.swift:541:27: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Alamofire: /Source/Core/Session.swift:572:27: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Alamofire: /Source/Features/Concurrency.swift:768:25: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Alamofire: /Tests/ConcurrencyTests.swift:484:30: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Alamofire: /Tests/ConcurrencyTests.swift:510:30: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Alamofire: /Tests/ConcurrencyTests.swift:538:30: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/App/iOS/Delegates/SceneDelegate.swift:304:22: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/App/iOS/Delegates/SceneDelegate.swift:315:17: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/DataTests/DomainTests.swift:67:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/DataTests/DomainTests.swift:78:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/DataTests/DomainTests.swift:103:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/DataTests/DomainTests.swift:300:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/DataTests/DomainTests.swift:367:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/DataTests/DomainTests.swift:420:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/URLFormatTests.swift:14:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/WebFilters/ResourceDownloaderStreamTests.swift:70:22: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/WebFilters/ResourceDownloaderStreamTests.swift:84:22: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/WebFilters/GroupedAdBlockEngineTests.swift:60:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/SearchTests.swift:18:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/SearchTests.swift:43:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/UniversalLinkManagerTests.swift:10:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/PageDataTests.swift:20:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/PageDataTests.swift:137:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/PageDataTests.swift:175:22: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/StringExtensionsTests.swift:11:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/TestFavicons.swift:14:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/TopBarToolbarVisibilityViewModelTests.swift:10:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/AdBlockEngineManagerTests.swift:128:22: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/SolanaProviderScriptHandlerTests.swift:14:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/ContentBlockerManagerTests.swift:136:22: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/ContentBlockerManagerTests.swift:145:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/ContentBlockerManagerTests.swift:213:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/ContentBlockerManagerTests.swift:259:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/ContentBlockerManagerTests.swift:291:22: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/UserScripts/FarblingProtectionHelperTests.swift:11:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/TabManagerTests.swift:115:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/UserScripts/ScriptExecutionTests.swift:48:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/UserScripts/ScriptExecutionTests.swift:85:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/UserScripts/ScriptExecutionTests.swift:174:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/UserScripts/ScriptExecutionTests.swift:233:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/ClientTests/UserScripts/ScriptExecutionTests.swift:496:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/BuyTokenStoreTest.swift:113:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/NetworkStoreTests.swift:13:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/DecentralizedDNSHelperTests.swift:13:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/AccountsStoreTests.swift:13:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/SelectAccountTokenStoreTests.swift:84:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/SwapTokenStoreTests.swift:639:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/SwapTokenStoreTests.swift:671:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/SwapTokenStoreTests.swift:709:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/KeyringStoreTests.swift:81:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/UserAssetsStoreTests.swift:159:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/TransactionParserTests.swift:1281:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/TransactionParserTests.swift:1362:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/TransactionParserTests.swift:1446:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/TransactionParserTests.swift:1528:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/SendTokenStoreTests.swift:1639:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/SendTokenStoreTests.swift:1689:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/SendTokenStoreTests.swift:1740:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/SendTokenStoreTests.swift:1814:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/NetworkSelectionStoreTests.swift:13:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/PortfolioStoreTests.swift:13:12: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveSharedTests/URLExtensionTests.swift:135:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/TransactionConfirmationStoreTests.swift:211:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/TransactionConfirmationStoreTests.swift:270:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/TransactionConfirmationStoreTests.swift:329:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/TransactionConfirmationStoreTests.swift:390:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/TransactionConfirmationStoreTests.swift:449:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/TransactionConfirmationStoreTests.swift:490:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/TransactionConfirmationStoreTests.swift:532:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/TransactionConfirmationStoreTests.swift:573:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/TransactionConfirmationStoreTests.swift:635:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/TransactionConfirmationStoreTests.swift:656:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveWalletTests/TransactionConfirmationStoreTests.swift:787:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveTalkTests/BraveTalkTests.swift:13:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveTalkTests/BraveTalkTests.swift:19:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/BraveTalkTests/BraveTalkTests.swift:25:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/PlaylistUITests/PlayerModelTests.swift:40:22: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/PlaylistUITests/PlayerModelTests.swift:72:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/PlaylistUITests/PlayerModelTests.swift:81:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/PlaylistUITests/PlayerModelTests.swift:96:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/PlaylistUITests/PlayerModelTests.swift:112:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/PlaylistUITests/PlayerModelTests.swift:136:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/PlaylistUITests/PlayerModelTests.swift:156:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/PlaylistUITests/PlayerModelTests.swift:176:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/PlaylistUITests/PlayerModelTests.swift:197:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/PlaylistUITests/PlayerModelTests.swift:223:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/PlaylistUITests/PlayerModelTests.swift:248:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/PlaylistUITests/PlayerModelTests.swift:280:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/PlaylistUITests/PlayerModelTests.swift:302:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/PlaylistUITests/PlayerModelTests.swift:325:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
📖	This PR fixed a violation in Brave: /ios/brave-ios/Tests/PlaylistUITests/PlayerModelTests.swift:341:14: Warning: Attributes should be on their own lines in functions and types, but on the same line as variables and imports (attributes)
⚠️	Danger found 6825 violations with this PR. Due to GitHub's max issue comment size, the number shown has been truncated to 137.

Generated by 🚫 Danger