Issue with latest release 6.8.3

[OlegApanovich]

For some reason, latest wordpress-stubs 6.8.3 started not to see all worpress functions in php version 7.4. Working fine with php 8.0 and above or wordpress-stubs 6.8.2 or below.

Environment:
PHP 7.4 version
Wordpress 6.8.3 version

Path to recreate.

1. In wordpress installation, create a new plugin with wpcli command
   wp scaffold plugin temp-plugin

2. Go to the newly created plugin directory
   cd wp-content/plugins/temp-plugin

3. Create a composer.json file there
   touch composer.json

4. Insert into the composer.json file

{
  "require-dev": {
    "phpstan/phpstan": "^2.1",
    "php-stubs/wordpress-stubs": "^6.8"
  }
}

5. Create phpstan.neon file
   touch phpstan.neon

6. Insert into the phpstan.neon file

parameters:
    level: 1
    paths:
        - temp-plugin.php
    scanFiles:
        - vendor/php-stubs/wordpress-stubs/wordpress-stubs.php

7. Insert into temp-plugin.php file for testing purposes one new line
   wp_get_available_translations();

8. Run the command
   composer install

9. Right now, launch the php stan check
   php vendor/bin/phpstan analyse

10. Observe the issue, there is an error in phpstan analysis

Note: Using configuration file /var/www/html/wp-content/plugins/temp-plugin/phpstan.neon.
 1/1 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100%

 ------ ---------------------------------------------------------------------- 
  Line   temp-plugin.php                                                       
 ------ ---------------------------------------------------------------------- 
  18     Function wp_get_available_translations not found.
         🪪  function.notFound                                                  
         💡  Learn more at https://phpstan.org/user-guide/discovering-symbols

[szepeviktor]

Hello! Try

parameters:
  bootstrapFiles:
    - vendor/php-stubs/wordpress-stubs/wordpress-stubs.php

instead.

[krompets]

I also use php74 and have an issue

vendor/php-stubs/wordpress-stubs/wordpress-stubs.php: syntax error, unexpected '{', expecting variable (T_VARIABLE)

it while run

./vendor/bin/phpstan analyze --no-progress --configuration ./phpstan.neon.dist

[szepeviktor]

I also use php74 and have an issue

#394

[IanDelMar]

This is most likely caused by PHP attributes and the PHP 7–incompatible pretty-printing behaviour of nikic/php-parser < 5.5, which was accidentally used to generate the WP 6.8.3 stubs.

@OlegApanovich @krompets
First thought: drop PHP 7.4 support in your project. 🙃 More constructive options:

• In your composer.json, require php-stubs/wordpress-stubs as dev-master. The current dev branch already contains the fix, and you’ll benefit from unreleased improvements (and php-stubs/wordpress-stubs benefits if you spot issues before a release – win-win).
• Ask Viktor to release Rebuild wordpress-stubs.php #394 as 6.8.3+1.
• Add a conflict entry for php-stubs/wordpress-stubs version 6.8.3 in your composer.json.
• Pin the version to 6.8.2 in your composer.json.
• Use a script that, on install/update, grabs the file from your vendor directory, replaces all instances of #[\SensitiveParameter] with an empty string, and places it in your project’s tests directory.

Please let us know if and which of these options worked for you, so that others facing the same issue can find a solution.

@szepeviktor
Yesterday I was about to note that the absence of issues about broken stubs strongly suggests that no one using the stubs is running PHP 7.4 – and to suggest dropping support. 😆

[OlegApanovich]

Hello! Try

parameters:
bootstrapFiles:
- vendor/php-stubs/wordpress-stubs/wordpress-stubs.php
instead.

Thank you, but it's not working, in such case I have fatal error
Fatal error: Cannot redeclare get_cli_args() (previously declared in /var/www/html/wp-admin/includes/class-wp-importer.php:282) in /vendor/php-stubs/wordpress-stubs/wordpress-stubs.php on line 82589

[szepeviktor]

Very useful!
It shows you include the source of WordPress core in your PHPStan config.
Please include only one!

• stubs
• or source

[OlegApanovich]

This is most likely caused by PHP attributes and the PHP 7–incompatible pretty-printing behaviour of nikic/php-parser < 5.5, which was accidentally used to generate the WP 6.8.3 stubs.

@OlegApanovich @krompets First thought: drop PHP 7.4 support in your project. 🙃 More constructive options:

• In your composer.json, require php-stubs/wordpress-stubs as dev-master. The current dev branch already contains the fix, and you’ll benefit from unreleased improvements (and php-stubs/wordpress-stubs benefits if you spot issues before a release – win-win).
• Ask Viktor to release Rebuild wordpress-stubs.php #394 as 6.8.3+1.
• Add a conflict entry for php-stubs/wordpress-stubs version 6.8.3 in your composer.json.
• Pin the version to 6.8.2 in your composer.json.
• Use a script that, on install/update, grabs the file from your vendor directory, replaces all instances of #[\SensitiveParameter] with an empty string, and places it in your project’s tests directory.

Please let us know if and which of these options worked for you, so that others facing the same issue can find a solution.

@szepeviktor Yesterday I was about to note that the absence of issues about broken stubs strongly suggests that no one using the stubs is running PHP 7.4 – and to suggest dropping support. 😆

Actually, I already downgraded to 6.8.2, it's all fine, no problem if it's only in the current version, and you are already aware of it, and it will be fixed in the next version. We will wait then.
Drop 7.4 is not an option for us now, WordPress core itself still supports 7.4.
Thank you guys for this great tool, and your support