-
Notifications
You must be signed in to change notification settings - Fork 2
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
How to run with custom rules? #8
Comments
What do you mean, "inflow defined rules"? If you mean custom rules, then there's a small amount of work, which I hope to smooth soon. First, define the rules in some namespace ( I am not entirely sure if you can do this with the Let me know if you need help. |
Oh sry, I mean "custom" rules. Thanks for the quick answer!. ❯ clj -M:splint -e "(require 'dev.rules)"
splint errors:
Unknown option: "-e" |
Ah damn, I thought that would work. Let me see if I can whip something up to help you out. |
Ah, I missed the crucial final bit. There are two ways to handle it.
I'll update the docs while I consider how best to handle this automatically. |
Okay, having thought about this for a little while, I have a solution in mind. I'd like your feedback before I begin implementation. There will be a new command-line flag This shouldn't be too hard to implement, so please let me know if that would suit your needs. |
I decided to implement it as described. Will be released shortly. Thanks! |
I ask what is the best way to start splint with inflow defined rules?
Is it possible to fork without splint?
The text was updated successfully, but these errors were encountered: