kkmuffme

hey, any update on this? would be great if it could be released

on a sidenote: `$_FILES[...]['tmp_name']` should not require sanitizing nor unslashing either, as that's set by PHP internally with random alphanumeric characters.

Yes I think the disallow string solution would make most sense. >Anything else is far too prone to false positives though, as plugins/themes often declare their own "root dir" in...

>I very much don't agree with this. Declaring a plugin/theme "root dir" in a constant using something like plugin_dir_path( __FILE__ ) is actually good practice and should not be discouraged....

Thanks for your feedback. Is there any ETA for the PHPCSUtils? Is there any possibility to create a new WPCS release with just this and perhaps https://github.com/WordPress/WordPress-Coding-Standards/issues/1583#issuecomment-1133985023 as this would...

>Did you mean that this behaviour isn't described in docs for zRange command? Yes

@yatsukhnenko fyi this is becoming a problem, since static analysis tools (psalm, phpstan) flag errors if we check for a false value, which is not declared in the @return type....

Same also reported here https://github.com/phpredis/phpredis/issues/1923

Could this please get fixed? psalm/phpstan are reporting errors basically everywhere, since the docs and stubs are incorrect.

This PR could also fix https://github.com/phpredis/phpredis/issues/1921, as the stubs are correct now. @michael-grunder could you apply those changes you did for the stubs also for the documentation, so it's correct...