Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D digitec-wiki
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Digitec
  • digitec-wiki
  • Wiki
  • php coding standards

php coding standards · Changes

Page history
mmclin: update naming conventions authored Mar 25, 2014 by Rene Cabral's avatar Rene Cabral
Show whitespace changes
Inline Side-by-side
php-coding-standards.markdown
View page @ ac5e5316
...@@ -147,6 +147,7 @@ The usage of these methods are only allowed when it is clear that there is a mai ...@@ -147,6 +147,7 @@ The usage of these methods are only allowed when it is clear that there is a mai
For many relations where the convention does not apply, the following methods must be used instead (where XXX is the name of the related thing): For many relations where the convention does not apply, the following methods must be used instead (where XXX is the name of the related thing):
``` ```
Main Relation Other Relations Main Relation Other Relations
get() getXXX() get() getXXX()
...@@ -164,6 +165,9 @@ count() countXXX() ...@@ -164,6 +165,9 @@ count() countXXX()
keys() n/a keys() n/a
``` ```
While "setXXX" and "replaceXXX" are very similar, there is one notable difference: "setXXX" may replace, or add new elements to the relation. "replaceXXX", on the other hand, cannot add new elements. If an unrecognized key as passed to "replaceXXX" it must throw an exception. While "setXXX" and "replaceXXX" are very similar, there is one notable difference: "setXXX" may replace, or add new elements to the relation. "replaceXXX", on the other hand, cannot add new elements. If an unrecognized key as passed to "replaceXXX" it must throw an exception.
......
Clone repository
  • alpha beta testing
  • browser testing
  • camtasia licenses
  • code delivery processes
  • coding practices
  • css and sass coding standards
  • database schema standards
  • dependency management
  • development environments
  • digitec agile process
  • digitec gitlab styles
  • digitec software promises
  • digitec spec process
  • gitlab administration
  • gitlab issues tags
View All Pages