ff21ff796c
Specify rule properties in attribute
2024-12-26 20:40:29 +01:00
cc4b569c54
Enable unused_parameter rule and fix all violations ( #5673 )
2024-07-14 11:20:50 -04:00
c810459e6a
Enforce mandatory trailing comma and fix all violations ( #5640 )
2024-06-28 05:36:50 +00: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
35a78815d1
Update SwiftSyntax ( #5198 )
2023-09-14 22:49:55 +02:00
b281a8d33a
Update SwiftSyntax ( #5168 )
2023-08-30 22:57:10 +02: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
1b1b19a902
Fix some unhandled_throwing_task false positives ( #5001 )
...
Fixes some of the cases reported in
https://github.com/realm/SwiftLint/issues/4987
2023-05-12 10:35:59 -04:00
e7bf813f15
Make unhandled_throwing_task rule opt-in ( #5000 )
...
Because since it was included in a release a few days ago, we've had
several reports of false positives and so flipping to opt-in is
appropriate so users can determine for themselves if they should enable
the rule.
2023-05-12 09:46:07 -04:00
87e230ce87
Fix false positive when result is accessed ( #4986 )
2023-05-10 20:36:00 -04:00
fa32fbc4f0
Minor edits to unhandled_throwing_task changelog entry
...
And rule description.
2023-05-10 14:04:42 -04:00
8822d40687
Add unhandled_throwing_task rule ( #4958 )
...
This rule will check Task's that are not explicitly annotated with success and
failure types for unhandled try expressions. These trys will silently fail if an
error is thrown.
See this forum thread for more details:
https://forums.swift.org/t/task-initializer-with-throwing-closure-swallows-error/56066
2023-05-10 14:03:01 -04:00
Danny Mösch
JP Simard
Kyle Bashour