f72f195ece
Fix error reporting ( #6061 )
2025-05-21 11:34:46 +01:00
82fd3e4058
Ensure that content is complete using an awaitable stream ( #5986 )
2025-02-10 22:59:43 +01:00
f796fee241
Enable strict concurrency checks in test code ( #5943 )
2025-01-07 22:19:25 +01:00
bef8acfb0e
Avoid NSRegularExpression in configurations ( #5921 )
2024-12-28 12:54:23 -05:00
dd157e2bdf
Use task-local variable ( #5919 )
2024-12-28 10:44:07 +01:00
1a54e3e313
Capture console on main actor only
2024-12-23 16:52:10 +01:00
a6c4fd98bc
Move files from SwiftLintCore to SwiftLintFramework
...
Ideally, SwiftLintCore would some day only contain components
that are needed to define rules. Consequently, it would be the
only bundle required to import for (external) rule development.
2024-12-23 12:51:43 +01:00
7385beaaf6
Add validation hook to configuration parsing ( #5824 )
2024-10-17 23:13:17 +02:00
63ee1944bd
Keep Swift 5 macOS build for the time being ( #5816 )
2024-10-01 15:25:03 +00:00
b903e0bd87
Sync strict concurrency build settings ( #5813 )
2024-09-29 15:22:07 -04:00
21b7e5ed6b
Enabled prefer_self_in_static_references, and fixed all current violations ( #5662 )
2024-07-10 18:58:27 +01:00
c29391a5ae
Ignore but report invalid keys ( #5567 )
...
Don't fall back to the default configuration due to invalid keys.
2024-05-11 10:28:10 +00:00
96db41c379
Add an experimental baseline feature ( #5475 )
2024-05-01 16:55:33 +02:00
5bbdf7f4e6
Allow to set configuration elements as deprecated ( #5540 )
...
Automatically print an appropriate warning to the console.
2024-04-25 19:37:04 +00:00
5075cc073c
Fix warnings about configured rules that are not enabled, when they are enabled in a parent config ( #4864 )
2024-03-25 21:39:22 +01:00
e6bb673444
Handle issues in nested contexts gracefully while still throwing standalone
...
Use different issues to make inlineable configurations work in both
scenarios, namely being used standalone and nested as part of another
configuration. In the latter case, finding no values to parse in a raw
configuration is okay, while as a standalone configuration it's not.
2024-03-24 09:36:18 +01:00
ccd50e8c68
Merge duplicated issues
2024-03-24 09:36:18 +01:00
082adfaed7
Fix some typos ( #5504 )
2024-03-23 15:25:16 +01:00
bedf211c43
Ignore absence of child or parent config instead of falling back to default ( #5407 )
2024-03-16 10:29:42 -04:00
fb4ef951ee
Print invalid keys when configuration parsing fails ( #5350 )
2023-11-14 23:43:38 +01: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
41b06629fd
Add new --silence-deprecation-warnings flag ( #5014 )
2023-06-20 16:03:22 -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
d73970e9d7
Remove error wrapper ( #5008 )
2023-05-16 18:22:25 +02:00
405113f793
Open ConfigurationError up to be used more broadly ( #5005 )
2023-05-14 20:00:46 +02:00
Martin Redington
Danny Mösch
deterclosed
Oleg Kohtenko