The expression return self::str_split($str) returns an array which contains values of type string[] which are incompatible with the documented value type string.
Loading history...
495
}
496
497
/**
498
* This method will auto-detect your server environment for UTF-8 support.
499
*
500
* @return true|null
501
*
502
* @internal <p>You don't need to run it manually, it will be triggered if it's needed.</p>
503
*/
504
4
public static function checkForSupport()
505
{
506
4
if (!isset(self::$SUPPORT['already_checked_via_portable_utf8'])) {
It seems like $options can also be of type null; however, parameter $options of filter_var() does only seem to accept array|integer, maybe add an additional type check?
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-type annotation
It seems like $definition can also be of type null; however, parameter $options of filter_var_array() does only seem to accept array|integer, maybe add an additional type check?
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-type annotation
This check compares calls to functions or methods with their respective definitions.
If the call has less arguments than are defined, it raises an issue.
If a function is defined several times with a different number of parameters, the
check may pick up the wrong definition and report false positives. One codebase
where this has been known to happen is Wordpress. Please note the @ignore annotation hint above.
It seems like $test3 can also be of type array; however, parameter $str of voku\helper\UTF8::count_chars() does only seem to accept string, maybe add an additional type check?
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-type annotation
It seems like $test3 can also be of type array; however, parameter $str of voku\helper\UTF8::count_chars() does only seem to accept string, maybe add an additional type check?
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-type annotation
* @param string $str <p>The string to be normalized.</p>
4633
* @param bool $keep_non_breaking_space [optional] <p>Set to true, to keep non-breaking-spaces.</p>
4634
* @param bool $keep_bidi_unicode_controls [optional] <p>Set to true, to keep non-printable (for the web)
4635
* bidirectional text chars.</p>
4636
* @param bool $normalize_control_characters [optional] <p>Set to true, to convert e.g. LINE-, PARAGRAPH-SEPARATOR with "\n" and LINE TABULATION with "\t".</p>
4637
*
4638
* @psalm-pure
4639
*
4640
* @return string
4641
* <p>A string with normalized whitespace.</p>
4642
*/
4643
public static function normalize_whitespace(
4644
string $str,
4645
bool $keep_non_breaking_space = false,
4646
bool $keep_bidi_unicode_controls = false,
4647
bool $normalize_control_characters = false
4648
): string {
4649
61
return ASCII::normalize_whitespace(
4650
61
$str,
4651
61
$keep_non_breaking_space,
4652
61
$keep_bidi_unicode_controls,
4653
61
$normalize_control_characters
4654
);
4655
}
4656
4657
/**
4658
* Calculates Unicode code point of the given UTF-8 encoded character.
4659
*
4660
* INFO: opposite to UTF8::chr()
4661
*
4662
* EXAMPLE: <code>UTF8::ord('☃'); // 0x2603</code>
4663
*
4664
* @param string $chr <p>The character of which to calculate code point.<p/>
4665
* @param string $encoding [optional] <p>Set the charset for e.g. "mb_" function</p>
4666
*
4667
* @psalm-pure
4668
*
4669
* @return int
4670
* <p>Unicode code point of the given character,<br>
4671
* 0 on invalid UTF-8 byte sequence</p>
4672
*/
4673
public static function ord($chr, string $encoding = 'UTF-8'): int
4674
{
4675
/**
4676
* @psalm-suppress ImpureStaticVariable
4677
*
4678
* @var array<string,int>
4679
*/
4680
27
static $CHAR_CACHE = [];
4681
4682
// init
4683
27
$chr = (string) $chr;
4684
4685
27
if ($encoding !== 'UTF-8' && $encoding !== 'CP850') {
The expression $code of type integer|null is loosely compared to true; this is ambiguous if the integer can be 0. You might want to explicitly use !== null instead.
In PHP, under loose comparison (like ==, or !=, or switch conditions),
values of different types might be equal.
For integer values, zero is a special case, in particular the following
results might be unexpected:
0==false// true0==null// true123==false// false123==null// false// It is often better to use strict comparison0===false// false0===null// false
The expression return self::str_ireplac...ch, $replacement, $str) could return the type string[] which is incompatible with the type-hinted return string. Consider adding an additional type-check to rule them out.
Loading history...
5237
}
5238
5239
/**
5240
* Replaces all occurrences of $search in $str by $replacement.
5241
*
5242
* @param string $str <p>The input string.</p>
5243
* @param array $search <p>The elements to search for.</p>
5244
* @param array|string $replacement <p>The string to replace with.</p>
5245
* @param bool $case_sensitive [optional] <p>Whether or not to enforce case-sensitivity. Default: true</p>
The expression return self::str_ireplac...ch, $replacement, $str) could return the type string[] which is incompatible with the type-hinted return string. Consider adding an additional type-check to rule them out.
Loading history...
5263
}
5264
5265
/**
5266
* Replace the diamond question mark (�) and invalid-UTF8 chars with the replacement.
It seems like you do not handle an error condition for mb_substitute_character(). This can introduce security issues, and is generally not recommended.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-unhandled annotation
If you suppress an error, we recommend checking for the error condition explicitly:
// For example instead of@mkdir($dir);// Better useif(@mkdir($dir)===false){thrownew\RuntimeException('The directory '.$dir.' could not be created.');}
Loading history...
5307
// the polyfill maybe return false, so cast to string
It seems like $save can also be of type true; however, parameter $substitute_character of mb_substitute_character() does only seem to accept integer|null|string, maybe add an additional type check?
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-type annotation
The expression return self::str_split_a...ry_to_use_mb_functions) returns the type array<mixed,string[]> which is incompatible with the documented return type string[].
* @param string|string[] $to [optional] <p>The string being translated to to.</p>
11136
*
11137
* @psalm-pure
11138
*
11139
* @return string
11140
* <p>This function returns a copy of str, translating all occurrences of each character in "from"
11141
* to the corresponding character in "to".</p>
11142
*/
11143
public static function strtr(string $str, $from, $to = ''): string
11144
{
11145
2
if ($str === '') {
11146
return '';
11147
}
11148
11149
2
if ($from === $to) {
11150
return $str;
11151
}
11152
11153
2
if ($to !== '') {
11154
2
if (!\is_array($from)) {
11155
2
$from = self::str_split($from);
11156
}
11157
11158
2
if (!\is_array($to)) {
11159
2
$to = self::str_split($to);
11160
}
11161
11162
2
$count_from = \count($from);
11163
2
$count_to = \count($to);
11164
11165
2
if ($count_from !== $count_to) {
11166
2
if ($count_from > $count_to) {
11167
2
$from = \array_slice($from, 0, $count_to);
11168
2
} elseif ($count_from < $count_to) {
11169
2
$to = \array_slice($to, 0, $count_from);
11170
}
11171
}
11172
11173
2
$from = \array_combine($from, $to);
11174
2
if ($from === false) {
11175
throw new \InvalidArgumentException('The number of elements for each array isn\'t equal or the arrays are empty: (from: ' . \print_r($from, true) . ' | to: ' . \print_r($to, true) . ')');
Are you sure print_r($from, true) of type string|true can be used in concatenation?
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-type annotation
11175
throw new \InvalidArgumentException('The number of elements for each array isn\'t equal or the arrays are empty: (from: ' . /** @scrutinizer ignore-type */ \print_r($from, true) . ' | to: ' . \print_r($to, true) . ')');
Are you sure print_r($to, true) of type string|true can be used in concatenation?
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-type annotation
11175
throw new \InvalidArgumentException('The number of elements for each array isn\'t equal or the arrays are empty: (from: ' . \print_r($from, true) . ' | to: ' . /** @scrutinizer ignore-type */ \print_r($to, true) . ')');
It seems like $to can also be of type array<mixed,string[]>; however, parameter $replace of str_replace() does only seem to accept string|string[], maybe add an additional type check?
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-type annotation
The expression $length of type integer|null is loosely compared to false; this is ambiguous if the integer can be 0. You might want to explicitly use === null instead.
In PHP, under loose comparison (like ==, or !=, or switch conditions),
values of different types might be equal.
For integer values, zero is a special case, in particular the following
results might be unexpected:
0==false// true0==null// true123==false// false123==null// false// It is often better to use strict comparison0===false// false0===null// false
Loading history...
11334
return '';
11335
}
11336
11337
// impossible
11338
4
if ($offset && $offset > $str_length) {
11339
return '';
11340
}
11341
11342
4
$length = $length ?? $str_length;
11343
11344
if (
11345
4
$encoding !== 'UTF-8'
11346
&&
11347
4
self::$SUPPORT['mbstring'] === false
11348
) {
11349
/**
11350
* @psalm-suppress ImpureFunctionCall - is is only a warning
It seems like $str can also be of type false; however, parameter $string of utf8_encode() does only seem to accept string, maybe add an additional type check?
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-type annotation
$class_array was never initialized. Although not strictly required by PHP, it is generally a good practice to add $class_array = array(); before regardless.