-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Rules file as argument to support multiple projects #1207
Comments
What were you envisioning for this? A commandline argument? A configuration option in the |
Either way would be great. I like the configuration option in the .yml idea best |
Maybe we could support external file references in whitelist_rules: `~/.swiftlint/common_rules.yml` |
I think in general it'd be better to have a |
This isn’t a native solution, but sharing configurations between projects is one of the reasons I started writing Workspace. If...
...Workspace should already be able to make SwiftLint share its configuration like you want. If your set‐up is more complicated, or if something below does not work properly, raise an issue at the Workspace repository, and I will look into it. Steps:
Thanks again to everyone at SwiftLint. Your work is much appreciated. |
I would love to reference the config file as a command line argument, or from within |
This issue has been automatically marked as stale because it has not had any recent activity. Please comment to prevent this issue from being closed. Thank you for your contributions! |
It would be nice to specify a rules file as a command line argument, to support having one set of rules for multiple projects.
The text was updated successfully, but these errors were encountered: