Remove unnecessary phan issue suppression
Make ApiQueryBase::addOption() annotation consistent with SelectQueryBuilder::option() since the ApiQueryBase method is just a wrapper to it. Change-Id: Ib301bce787c8ba89ae8333eb7cfb8d7d287de20c
This commit is contained in:
parent
320af70270
commit
930f6fbe20
2 changed files with 1 additions and 2 deletions
|
|
@ -373,7 +373,7 @@ abstract class ApiQueryBase extends ApiBase {
|
|||
* Add an option such as LIMIT or USE INDEX. If an option was set
|
||||
* before, the old value will be overwritten
|
||||
* @param string $name Option name
|
||||
* @param int|string|string[]|null $value Option value
|
||||
* @param mixed $value The option value, or null for a boolean option
|
||||
*/
|
||||
protected function addOption( $name, $value = null ) {
|
||||
$this->getQueryBuilder()->option( $name, $value );
|
||||
|
|
|
|||
|
|
@ -189,7 +189,6 @@ class ApiQueryLogEvents extends ApiQueryBase {
|
|||
|
||||
// T71222: MariaDB's optimizer, at least 10.1.37 and .38, likes to choose a wildly bad plan for
|
||||
// some reason for this code path. Tell it not to use the wrong index it wants to pick.
|
||||
// @phan-suppress-next-line PhanTypeMismatchArgument
|
||||
$this->addOption( 'IGNORE INDEX', [ 'logging' => [ $index ] ] );
|
||||
}
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue