Browse Source

doc typos

tags/2.0.0-beta
Carsten Brandt 11 years ago
parent
commit
2fb823a04d
  1. 4
      docs/guide/extensions.md

4
docs/guide/extensions.md

@ -6,8 +6,8 @@ Code style
- Extension code style should be similar to [core framework code style](https://github.com/yiisoft/yii2/wiki/Core-framework-code-style). - Extension code style should be similar to [core framework code style](https://github.com/yiisoft/yii2/wiki/Core-framework-code-style).
- In case of using getter and setter for defining a property it's preferred to use method in extension code rather than property. - In case of using getter and setter for defining a property it's preferred to use method in extension code rather than property.
- All classes, methods and properties should be documented using phpdoc. Note that you can use markdown and like to API - All classes, methods and properties should be documented using phpdoc. Note that you can use markdown and link to properties and methods
documents using `[[name()]]`. using the following syntax: e.g. `[[name()]]`, `[[name\space\MyClass::name()]]`.
- If you're displaying errors to developers do not translate these (i.e. do not use `\Yii::t()`). Errors should be - If you're displaying errors to developers do not translate these (i.e. do not use `\Yii::t()`). Errors should be
translated only if they're displayed to end users. translated only if they're displayed to end users.

Loading…
Cancel
Save