Integrate Sniffs with WP-CLI

[westonruter]

We could introduce a new WP-CLI subcommand called lint or phpcs which would apply the sniffs in this project to the WordPress install in the current scope.

I'm not sure of the best route to go as for integrating the sniffs into WP-CLI. Perhaps it would mean forking WP-CLI https://github.com/wp-cli/wp-cli and then adding this repo as a submodule dependency.

[Rarst]

There is ongoing discussion about creating package system for WP-CLI which seems to be trending towards exploring Composer for it wp-cli/wp-cli#424

[pixline]

I gave the wp phpcs command a try within my wp-cli php devtools.

Of course I can't say it's the best implementation but it's a working draft at least. Criticisms and/or suggestions are really appreciated.

[GaryJones]

What's the status on this from the WP-CLI side? (I'm not familiar with WP-CLI)

[Rarst]

I am a little "why bother" on this. What does running it with wpcli does which is better than... just running it?

[GaryJones]

I am a little "why bother" on this. What does running it with wpcli does which is better than... just running it?

That's a good point. If one has command-line access to run WP-CLI, then one could also use the command line to do phpcs too.

Might be some advantage to being able to have WP-CLI loop through each plugin and theme and trigger phpcs for each with any custom phpcs.xml? It's not really how many folks work though.

[danielbachhuber]

What does running it with wpcli does which is better than... just running it?

I don't see much utility in a WP-CLI command for running phpcs.

[Rarst]

@westonruter do you have any additional thoughts on what merit of such command could be?

[westonruter]

No. I don't remember why I thought this was a good idea 😄