599e51a5a2
Format code ( #6151 )
2025-07-02 17:50:53 -04:00
5517d233fd
Started to add rationales ( #5681 )
2025-03-06 10:16:30 +00:00
ff21ff796c
Specify rule properties in attribute
2024-12-26 20:40:29 +01:00
cffb331009
Fix spurious Bazel build errors ( #5756 )
2024-08-18 20:53:57 +00:00
2442e10f13
Avoid needless indentation in examples ( #5675 )
2024-07-16 13:57:05 -04:00
c810459e6a
Enforce mandatory trailing comma and fix all violations ( #5640 )
2024-06-28 05:36:50 +00:00
c730047176
Enable superfluous_else rule ( #5412 )
2024-03-03 16:30:44 +01:00
40bd97038a
Support arbitrary configurations in @SwiftSyntaxRule ( #5275 )
...
Almost all rules based on SwiftSyntax can be set up now by just adding
`@SwiftSyntaxRule` to the rule struct.
2023-10-16 19:34:43 +02:00
2ed1fc2f27
Let all rules be configurable ( #5274 )
2023-10-12 17:30:45 +02:00
591154091e
Introduce @SwiftSyntaxRule & @Fold macros ( #5253 )
...
These macros remove some of the boilerplate involved when writing rules.
This change also adds test infrastructure for the macros used within
SwiftLint.
2023-10-02 18:43:16 -04:00
b281a8d33a
Update SwiftSyntax ( #5168 )
2023-08-30 22:57:10 +02:00
f10fc3056b
Remove superfluous newline characters from examples ( #5158 )
2023-08-06 12:23:26 -04:00
3f039f26d5
Connect configs with their referencing rules to have some context in error logging ( #5017 )
...
With the binding of configurations to their associated rule types
"unknown configuration" errors can be made more specific mentioning
also the rule's identifier in the printed message.
2023-05-19 20:58:24 +02:00
a7bc9e20c7
Move built-in rules to new SwiftLintBuiltInRules module ( #4950 )
2023-04-27 11:16:01 -04:00
Danny Mösch
Martin Redington
JP Simard