Skip to end of metadata
Go to start of metadata

<p>This page contains a list of proposals for different additions/modifications to curent ZF coding strandards.</p>

<p>Right now additions include:</p>
<ul>
<li><a href="http://framework.zend.com/wiki/x/NoDZAg">Class Naming Conventions</a></li>
<li><a href="http://framework.zend.com/wiki/x/M4DZAg">Method Naming Conventions</a></li>
</ul>

<p>Later this page will include voting. Please discuss above addendums on respective pages or mailing list.</p>

Labels:
rfc rfc Delete
coding+standards coding+standards Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Apr 17, 2012

    <p>I'm going to be blunt: If we do any further changes at this point, I'd argue they should only be towards PSR-1 compliance (<a class="external-link" href="https://github.com/php-fig/fig-standards/pull/25/files">https://github.com/php-fig/fig-standards/pull/25/files</a>). I'd rather not derail development of ZF2 further for a drawn out discussion of naming conventions. Yes, we can likely name a few things better (per the discussion about boolean accessors on the ML), but these are trivial, and I don't feel need to be codified.</p>

    1. Apr 17, 2012

      <p>I agree, there should be no lengthy discussion, and the list should have up to 5-10 point (probably I should compile it into one page).<br />
      Anyway, final decision on standards is up to ZF core team, but let me let people on ML know.<br />
      One important thing here is modules. I think module developers should have at least some basic standards to know how to code modules "ZF2 way", that includes plugin loading, Options, factories, setters/getters.<br />
      As for PSR-1, don't have any opinion yet, need to study it first.</p>