I am not sure that is true, I personally don’t want my lint rules to be located in application code.
I will soon start going deeper in the topic of heavy linting of the project and then maybe I will have more insights on downsides of each approach.
D4no0
thiagomajesk
Ok, I see what you mean now. The way I read the question seemed more like an application concern to block specific calls, but the idea is to check arbitrary functions across the application (and probably across boundaries). I’m glad you found a solution.
Cheers!
1
sodapopcan
Apologies for the continued commenting here but I was doing a bit more of this stuff and I realized that it isn’t checking for single pipe, it’s checking for the piped version. Since the AST is different I believe the only way is to check for both versions but perhaps there is a cleaner way?
0
krasenyp
Yes, I tried on a codebase littered with piped keyword assigns and at some point I saw many false negatives. I played with the rule but couldn’t find a better approach.
0
sodapopcan
Oh! Do you have an example? I only ever used it on a codebase that I was the only developer on and of course I didn’t try and break the rules often 
It grew pretty sizeable, though.
0