Remove WP\Functions::__ and other translate functions

Under the new sniffer rules, those functions produce errors and, when those methods
are used, the sniffer can not properly be applied.

[MAILPOET-4524]
This commit is contained in:
David Remer
2022-08-04 12:54:09 +03:00
committed by Veljko V
parent 0b2b211b08
commit b05e6d414c
156 changed files with 645 additions and 719 deletions

View File

@ -9,7 +9,6 @@ use MailPoet\API\JSON\ResponseBuilders\CustomFieldsResponseBuilder;
use MailPoet\Config\AccessControl;
use MailPoet\CustomFields\CustomFieldsRepository;
use MailPoet\Entities\CustomFieldEntity;
use MailPoet\WP\Functions as WPFunctions;
class CustomFields extends APIEndpoint {
public $permissions = [
@ -45,7 +44,7 @@ class CustomFields extends APIEndpoint {
return $this->successResponse($this->customFieldsResponseBuilder->build($customField));
} else {
return $this->errorResponse([
APIError::NOT_FOUND => WPFunctions::get()->__('This custom field does not exist.', 'mailpoet'),
APIError::NOT_FOUND => __('This custom field does not exist.', 'mailpoet'),
]);
}
}
@ -68,7 +67,7 @@ class CustomFields extends APIEndpoint {
return $this->successResponse($this->customFieldsResponseBuilder->build($customField));
}
return $this->errorResponse([
APIError::NOT_FOUND => WPFunctions::get()->__('This custom field does not exist.', 'mailpoet'),
APIError::NOT_FOUND => __('This custom field does not exist.', 'mailpoet'),
]);
}
}