<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Wed, 19 Jun 2013 11:15:10 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Stefan Priebsch's Blog: Custom Coding Standards with PHP_CodeSniffer]]></title>
      <guid>http://www.phpdeveloper.org/news/10541</guid>
      <link>http://www.phpdeveloper.org/news/10541</link>
      <description><![CDATA[<p>
<i>Stefan Priebsch</i> <a href="http://inside.e-novative.de/archives/124-Custom-Coding-Standards-with-PHP_CodeSniffer.html">recently posted</a> about his struggles with creating a custom coding started with the <a href="http://inside.e-novative.de/exit.php?url_id=1295&entry_id=124">PHP_CodeSniffer</a> package:
</p>
<blockquote>
In CodeSniffer, a coding standard is basically represented by an empty class that extends PHP_CodeSniffer_Standards_CodingStandard. I could not get the CodeSniffer to find my coding standard, though, and found the documentation lacking about where to put it, how to name it, and how to refer to it in the --standard switch.
</blockquote>
<p>
After an email to <a href="http://inside.e-novative.de/exit.php?url_id=1298&entry_id=124">Greg Sherwood</a> (developer of the package</a>) <i>Stefan</i> figured out his issue and has <a href="http://inside.e-novative.de/archives/124-Custom-Coding-Standards-with-PHP_CodeSniffer.html">shared the solution</a> in this post (step by step).
</p>]]></description>
      <pubDate>Thu, 03 Jul 2008 12:02:36 -0500</pubDate>
    </item>
  </channel>
</rss>
