Closed davisben closed 3 years ago
Hi @davisben, thanks so much for submitting this PR! I actually had this in place, but temporarily removed it as I was researching some issues. I'll go ahead and add it back in. Closing this PR, as I already have the code.
@davisben just FYI: I have pushed a few new version since yesterday, one of which includes this feature. Let me know how it works for you. :) Thanks again for submitting the issue and PR!
Looks good here. Thanks for your work on this!
That's awesome! Thanks for the feedback. Out of curiosity, what is your use-case for needing to customize the executable? (The only reason I currently need to customize it is to load a custom CodeSniffer.conf
file.) I'm eager to learn of other use-cases that I can keep in mind while improving functionality.
Thanks! ~Mike
I have some standards installed by composer that weren't being found by the included executable, so by setting the path to the phpcs executable in vendor/bin, those standards were found.
Ah, yes! I'm doing the same. Was thinking of letting the user provide a path to their CodeSniffer.conf
standards file and let it load that one, regardless of where PHPCS is installed. Still working on that. :)
Resolves #1