2018-04-05 07:04:08 +00:00
|
|
|
{
|
|
|
|
"name": "wordpress/wordpress",
|
|
|
|
"license": "GPL-2.0-or-later",
|
2018-04-05 07:15:25 +00:00
|
|
|
"description": "WordPress is open source software you can use to create a beautiful website, blog, or app.",
|
2018-04-05 07:04:08 +00:00
|
|
|
"homepage": "https://wordpress.org",
|
|
|
|
"keywords": [
|
|
|
|
"blog", "cms", "wordpress", "wp"
|
|
|
|
],
|
|
|
|
"support": {
|
|
|
|
"issues": "https://core.trac.wordpress.org/"
|
|
|
|
},
|
2019-09-20 17:32:23 +00:00
|
|
|
"require": {
|
2024-02-08 09:11:43 +00:00
|
|
|
"ext-json": "*",
|
2024-04-11 21:09:49 +00:00
|
|
|
"php": ">=7.2.24"
|
2019-09-20 17:32:23 +00:00
|
|
|
},
|
Script Loader: Use `wp_get_script_tag()` and `wp_get_inline_script_tag()`/`wp_print_inline_script_tag()` helper functions to output scripts on the frontend and login screen.
Using script tag helper functions allows plugins to employ the `wp_script_attributes` and `wp_inline_script_attributes` filters to inject the `nonce` attribute to apply Content Security Policy (e.g. Strict CSP). Use of helper functions also simplifies logic in `WP_Scripts`.
* Update `wp_get_inline_script_tag()` to wrap inline script in CDATA blocks for XHTML-compatibility when not using HTML5.
* Ensure the `type` attribute is printed first in `wp_get_inline_script_tag()` for back-compat.
* Wrap existing `<script>` tags in output buffering to retain IDE supports.
* In `wp_get_inline_script_tag()`, append the newline to `$javascript` before it is passed into the `wp_inline_script_attributes` filter so that the CSP hash can be computed properly.
* In `the_block_template_skip_link()`, opt to enqueue the inline script rather than print it.
* Add `ext-php` to `composer.json` under `suggest` as previously it was an undeclared dependency for running PHPUnit tests.
* Update tests to rely on `DOMDocument` to compare script markup, normalizing unsemantic differences.
Props westonruter, spacedmonkey, flixos90, 10upsimon, dmsnell, mukesh27, joemcgill, swissspidy, azaozz.
Fixes #58664.
See #39941.
git-svn-id: https://develop.svn.wordpress.org/trunk@56687 602fd350-edb4-49c9-b593-d223f7449a82
2023-09-25 21:03:19 +00:00
|
|
|
"suggest": {
|
|
|
|
"ext-dom": "*"
|
|
|
|
},
|
2018-04-05 07:04:08 +00:00
|
|
|
"require-dev": {
|
2024-09-19 12:38:35 +00:00
|
|
|
"squizlabs/php_codesniffer": "3.10.3",
|
2024-04-12 12:15:58 +00:00
|
|
|
"wp-coding-standards/wpcs": "~3.1.0",
|
2021-12-31 13:53:19 +00:00
|
|
|
"phpcompatibility/phpcompatibility-wp": "~2.1.3",
|
Build/Test Tools: Update PHPUnit Polyfills to version 1.1.0.
[https://github.com/sebastianbergmann/phpunit/blob/9.6/ChangeLog-9.6.md#961---2023-02-03 PHPUnit 9.6.1] deprecated the `assertObjectHasAttribute()` and `assertObjectNotHasAttribute()` methods, leading to deprecation notices in a number of tests.
[https://github.com/sebastianbergmann/phpunit/blob/10.1.3/ChangeLog-10.1.md#1010---2023-04-14 PHPUnit 10.1.0] brought the methods back by popular request, though renamed as `assertObjectHasProperty()` and `assertObjectNotHasProperty()`, to prevent confusion with PHP 8.0 attributes.
This meant that users which cannot (yet) upgrade to PHPUnit 10.1+ would always have deprecation notices for these methods without recourse. So, after much discussion, the new methods have been backported to [https://github.com/sebastianbergmann/phpunit/blob/9.6/ChangeLog-9.6.md#9611---2023-08-19 PHPUnit 9.6.11], leaving just the 10.0.x series with a deprecation notice and no recourse.
What does this mean for WordPress?
WordPress uses the [https://github.com/Yoast/PHPUnit-Polyfills PHPUnit Polyfills] to be able to write tests for the most recent versions of PHPUnit, with the Polyfills taking care of polyfilling any new PHPUnit methods on older PHPUnit versions.
* The PHPUnit Polyfills 1.x series supports PHPUnit 4.x to 9.x.
* The PHPUnit Polyfills 2.x series supports PHPUnit 5.x to 10.x.
WordPress currently runs against PHPUnit 6.x to 9.x with PHPUnit Polyfills 1.x, while the new methods were previously only included in PHPUnit Polyfills 2.0.0+, as they were introduced in PHPUnit 10.x.
Since the `assertObjectHasProperty()` and `assertObjectNotHasProperty()` methods have been backported to PHPUnit 9.x, the PHPUnit Polyfills will now include these methods in the 1.x series as well.
By upgrading to the latest [https://github.com/Yoast/PHPUnit-Polyfills/releases/tag/1.1.0 PHPUnit Polyfills 1.1.0] release, we can get rid of the deprecation notices related to the use of the `assertObjectHasAttribute()` and `assertObjectNotHasAttribute()` methods.
This could have implications for plugins or themes running integration tests with WordPress if they have set their PHPUnit Polyfills dependency to a fixed version or have a too strict version constraint (limiting the PHPUnit Polyfills to the 1.0.x series). The solution for those plugins or themes is to update their version constraints for the PHPUnit Polyfills to allow for the 1.1.x series.
Follow-up to [51559], [51598].
Props jrf, ayeshrajans.
Fixes #59150.
git-svn-id: https://develop.svn.wordpress.org/trunk@56421 602fd350-edb4-49c9-b593-d223f7449a82
2023-08-21 15:53:04 +00:00
|
|
|
"yoast/phpunit-polyfills": "^1.1.0"
|
2020-09-23 13:52:02 +00:00
|
|
|
},
|
2021-12-23 20:10:29 +00:00
|
|
|
"config": {
|
|
|
|
"allow-plugins": {
|
|
|
|
"dealerdirect/phpcodesniffer-composer-installer": true
|
2024-09-23 22:15:11 +00:00
|
|
|
},
|
|
|
|
"lock": false
|
2021-12-23 20:10:29 +00:00
|
|
|
},
|
2018-04-05 07:04:08 +00:00
|
|
|
"scripts": {
|
2019-09-25 13:46:55 +00:00
|
|
|
"compat": "@php ./vendor/squizlabs/php_codesniffer/bin/phpcs --standard=phpcompat.xml.dist --report=summary,source",
|
2019-09-25 14:01:51 +00:00
|
|
|
"format": "@php ./vendor/squizlabs/php_codesniffer/bin/phpcbf --report=summary,source",
|
|
|
|
"lint": "@php ./vendor/squizlabs/php_codesniffer/bin/phpcs --report=summary,source",
|
2020-06-01 20:29:06 +00:00
|
|
|
"lint:errors": "@lint -n",
|
2022-09-29 14:43:06 +00:00
|
|
|
"test": [ "Composer\\Config::disableProcessTimeout", "@php ./vendor/phpunit/phpunit/phpunit" ]
|
2018-04-05 07:04:08 +00:00
|
|
|
}
|
|
|
|
}
|