Skip to content

PHPCS should output to terminal on validate, generate report on analyze #1

@grayside

Description

@grayside

The current integration with PHPCS generates a report, and never denies a build. This means it is up to Jenkins reporting to point out problems with coding style. Reports like that are generally not useful to a developer's hourly workflow, but in-line reporting is something else.

Let's refocus the analyze task on generating reports, and the validate task on (time-efficient) terminal output.

To that end I've begun examining SaschaGalley/grunt-phpcs#20, but that PR seems broken in several ways.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions