Skip to content

Conversation

@ABaldwinHunter
Copy link
Contributor

See individual commits for changes.
@codeclimate/review

@ABaldwinHunter
Copy link
Contributor Author

README.md Outdated
phpcodesniffer:
enabled: true
config:
standard: "phpcs.ruleset.xml"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this information also live on our docs site? If so, should we link there to avoid going out of sync?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope it doesn't. The doc site has trailed the Readme

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was actually going to add a link in the other direction

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was it intentional to make this a first-class section? I think it'd be simpler to do what we do for PHPMD, by including a relative-ruleset in the existing example configuration.

engines: phpmd: enabled: true config: file_extensions: "php" rulesets: "unusedcode,codesize,naming,optional_relative_path_to_custom_ruleset.xml"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Meh. I think it could merit its own section here since there's also a section specifically devoted to standards besides the default (PSR1 and PSR2) that we support but don't feel strongly.

Copy link

@pbrisbin pbrisbin Aug 22, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it could merit its own section here since there's also a section specifically devoted to standards besides the default (PSR1 and PSR2) that we support

I probably wouldn't agree with that reasoning: the config showing an example of specifying a coding standard, then a section listing the available standards makes sense -- you need both those pieces of distinct information. But an example showing that you can point to a relative file stands alone. Having it out in another section with additional copy and another config example block isn't analogous, IMO.

Maybe someone like @leftees should be the ultimate reviewer on this PR.

@ABaldwinHunter
Copy link
Contributor Author

ping @leftees @pbrisbin

I think an explicit custom configuration section makes sense, but am happy to go with a simpler design.

@ABaldwinHunter
Copy link
Contributor Author

@leftees made explanation smaller as discussed. Ready for another look!

@leftees
Copy link
Contributor

leftees commented Aug 24, 2016

@ABaldwinHunter ABaldwinHunter merged commit 98cab36 into master Aug 24, 2016
@ABaldwinHunter ABaldwinHunter deleted the abh-readme branch August 24, 2016 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants