4078e41f1b
Let all rewriters have a configuration by default ( #5467 )
2024-02-11 15:13:24 +01:00
4c0f33782c
Check disabled regions for all syntax types in parent rewriter class ( #5292 )
2023-10-23 15:34:51 -04:00
57632017e4
Introduce parent class for rewriters ( #5282 )
2023-10-17 18:55:02 +02: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
58928b7e40
Enforce any on existential types ( #5273 )
...
This makes syntactically clear which types are rather expensive.
2023-10-12 08:37:23 +02:00
6438c77b96
Harmonize rule extensions ( #5272 )
2023-10-11 19:39:38 +02: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
fe312a06fe
Rely on pre-defined issues and allow to print them directly to the console ( #5013 )
...
Advantages of having typical errors at a common place:
* Error message styling can be harmonized
* Existing messages can be reused
* Overview of prefixes ('error: ', 'warning: ')
* Manage how to print them to the console
2023-05-16 20:15:14 +02:00
1fa8e484c4
Add expiring TODO comments on deprecation warnings
2023-05-10 21:44:20 +02:00
71b89e66de
Prepend warning: to error messages ( #4927 )
2023-05-01 18:26:25 +02:00
a7bc9e20c7
Move built-in rules to new SwiftLintBuiltInRules module ( #4950 )
2023-04-27 11:16:01 -04:00
Danny Mösch
Chris White
JP Simard