Congratulations! Your team has chosen a coding standard to use and you’re well on your way to a consistent code style for all your projects. But… there are some extra things you’d like to check for, some rules you really can’t be bothered with and some which sort of fit your needs, but not completely. Now what?

Come and learn how to make the PHP Codesniffer work for you and how to streamline the PHPCS related work-flow along the way.

Comments

Comments are closed.

Brilliant! Lot's of good practices shown, gave me a lot of ideas on what to improve in my current usage of phpcs. Also, presented in an excellent and easy to follow manner!

Great talk! I never realised how many features PHPCS actually had, as well as how much it can be configured. Very well presented with clear examples. Definitely a lot to take away. Thanks!

A very informative talk. Thank you.
Found out about features I didn't know existing.

Koen Eelen at 23:54 on 9 Jun 2017

Excellent talk, i finally understand how a phpcs.xml file is build.
Only thing I would have liked to see (but you cannot give 4.5 stars ;) ) is how to actually build your own sniff.
I have no idea how difficult it is, but I have the feeling that Juliette could give a great explanation of it. :)

Also bonus points for enthusiasm !

Wim Godden at 15:50 on 10 Jun 2017

Really nice talk, both giving a nice overview as well as some very nice tips & tricks along the way.

Mark Railton at 16:29 on 10 Jun 2017

Brilliant talk. Helped massively as I have been working with PHPCS quite a bit lately on a project at work.

Katy Ereira at 20:19 on 10 Jun 2017

I hadn't considered how many ways PHPCS could have helped me out. I came away feeling quite inspired and ready to implement some of these tricks in my projects!

Chris Emerson at 22:31 on 10 Jun 2017

I enjoyed this talk - PHPCS's documentation had been a bit lacking in 2.0, so while I'd used the tool for a while, I struggled to make best use of it. It looks like the new version (3.0) has better documentation and the talk introduced some things I hadn't known about before. The only thing I think that was missing that I would have liked to have seen is a small example or guide to writing custom sniffs - something I've thought about in the past but not looked into because of the lack of documentation.

Peter Fisher at 23:11 on 10 Jun 2017

Great talk. I learnt a lot of things thatI didn't realize PHPCS could do.
Thank you for adding that explain option. That is going to save me a load of time in the future!

Luna Chen at 23:38 on 10 Jun 2017

Amazing talk! I learned a lot about PHPSC, I didn't know you can do so much more with PHPCS other than styling fixes!

P.S the tip about before_install for travis script was super sweet! You read my mind when you said "I think some of you are thinking of fixing your travis script"! :)

Lee Boynton at 18:54 on 11 Jun 2017

Learnt a lot of things I didn't realise PHPCS does, such as sniffing for TODO comments and how to report on them.

It might have been good to know how the JS/CSS sniffs work, and how JS sniffs compare with a JS tool like jshint/jslint/eslint. That said, it felt like this talk already had a lot of information in it.

Gary Jones at 23:46 on 11 Jun 2017

Well presented, with live examples of how PHPCS works. I already use PHPCS a lot and knew many of the tips, but there were nuggets of information in here that were new to me too!

Naomi Gotts at 19:35 on 12 Jun 2017

Had no idea what phpcs was before the talk and now I do... Look forward to giving it a go on the work codebase sometime soon!

I did not know PHPCS could do more than and it has encouraged me to look into the other features when I come to update my project soon. Was clearly given and very informative.

My only issue was that it was mainly focusing on the code sniffer part and felt like the other features could have had more screen time, even if they were simple examples.

Good and informative talk. I've learned some new tricks, even though I considered myself fairly familiar with phpcs!