-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disabling custom rules from within a nested yml file throws warning #3521
Comments
I am seeing same thing! I am not able to disable a custom rule that's mentioned in the parent config |
I'd be happy to look into this but I have a backlog of about ~400+ SwiftLint issues and PRs that I'm going through, so it would really help me if you could simplify this to the most minimal repro case, ideally a zip archive of a directory where I can just run |
This is probably a duplicate of #3472. I created a fix for that but it broke something else and had to be (temporarily) reverted (see #3503 (comment)). In the coming days I will try to create a proper fix and will drop you a notice once it's done so that you can figure whether it also fixes your specific issue. |
Thanks for that context, @fredpi ! |
@tobiasjordan I believe this is probably fixed via #3538. Could you confirm this? (You can download the current |
@tobiasjordan There's now also 0.43.0 Release Candidate 4 which includes the potential fix for this issue. |
New Issue Checklist
Describe the bug
I get a warning when disabling a custom rule, defined in the top-level config file from within a nested config file:
warning: 'non_custom_localization' is not a valid rule identifier
.Complete output when running SwiftLint, including the stack trace and command used
Environment
The main file
.swiftlint.yml
is at the project root, the nested file atFolder1/Folder2/Folder3/.swiftlint.yml
with the following content:Xcode 12.2, Build version 12B45
No code directly triggers this, it's a general issue with the config file.
I found an existing already closed issue for this back in October 2018: #2441
Since this issue has appeared only recently without changes on my side, I'm assuming a recent change for Swiftlint broke something?
The text was updated successfully, but these errors were encountered: