Browse Source

blacklist → exclude (#18104)

tags/2.0.36
Brandon Kelly 4 years ago committed by GitHub
parent
commit
ba7106564d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 2
      docs/guide/rest-resources.md
  2. 4
      docs/guide/runtime-logging.md
  3. 2
      docs/guide/structure-filters.md
  4. 2
      docs/guide/structure-models.md

2
docs/guide/rest-resources.md

@ -82,7 +82,7 @@ public function fields()
} }
// filter out some fields, best used when you want to inherit the parent implementation // filter out some fields, best used when you want to inherit the parent implementation
// and blacklist some sensitive fields. // and exclude some sensitive fields.
public function fields() public function fields()
{ {
$fields = parent::fields(); $fields = parent::fields();

4
docs/guide/runtime-logging.md

@ -142,8 +142,8 @@ the pattern `yii\db\*`.
If you do not specify the [[yii\log\Target::categories|categories]] property, it means the target will process If you do not specify the [[yii\log\Target::categories|categories]] property, it means the target will process
messages of *any* category. messages of *any* category.
Besides whitelisting the categories by the [[yii\log\Target::categories|categories]] property, you may also In addition to specifying allowed categories using the [[yii\log\Target::categories|categories]] property, you may also
blacklist certain categories by the [[yii\log\Target::except|except]] property. If the category of a message exclude certain categories by the [[yii\log\Target::except|except]] property. If the category of a message
is found or matches one of the patterns in this property, it will NOT be processed by the target. is found or matches one of the patterns in this property, it will NOT be processed by the target.
The following target configuration specifies that the target should only process error and warning messages The following target configuration specifies that the target should only process error and warning messages

2
docs/guide/structure-filters.md

@ -34,7 +34,7 @@ public function behaviors()
By default, filters declared in a controller class will be applied to *all* actions in that controller. You can, By default, filters declared in a controller class will be applied to *all* actions in that controller. You can,
however, explicitly specify which actions the filter should be applied to by configuring the however, explicitly specify which actions the filter should be applied to by configuring the
[[yii\base\ActionFilter::only|only]] property. In the above example, the `HttpCache` filter only applies to the [[yii\base\ActionFilter::only|only]] property. In the above example, the `HttpCache` filter only applies to the
`index` and `view` actions. You can also configure the [[yii\base\ActionFilter::except|except]] property to blacklist `index` and `view` actions. You can also configure the [[yii\base\ActionFilter::except|except]] property to prevent
some actions from being filtered. some actions from being filtered.
Besides controllers, you can also declare filters in a [module](structure-modules.md) or [application](structure-applications.md). Besides controllers, you can also declare filters in a [module](structure-modules.md) or [application](structure-applications.md).

2
docs/guide/structure-models.md

@ -478,7 +478,7 @@ public function fields()
} }
// filter out some fields, best used when you want to inherit the parent implementation // filter out some fields, best used when you want to inherit the parent implementation
// and blacklist some sensitive fields. // and exclude some sensitive fields.
public function fields() public function fields()
{ {
$fields = parent::fields(); $fields = parent::fields();

Loading…
Cancel
Save