You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow PHP version to be changed from Site Settings (#225)
* Display the PHP version on Site Settings screen
* Add a modal for editing the PHP version
* First pass at saving selected PHP version
* Update site details to allow user to set PHP version (#226)
* Add phpVersion to updateSiteDetails
* Update tests for changing the PHP version
* Abstract available PHP versions to a constant
* Use PHP constants from `wp-now` (#231)
* Use `DEFAULT_PHP_VERSION` constant from `wp-now`
* Use available PHP versions of Playground
* Add `web-streams-polyfill` package for unit tests
* Polyfill `ReadableStream` in unit tests
Web streams are used by `php-wasm`, so we need to polyfull them if we import the library in unit tests.
* Add unit tests to cover changing PHP version functionality (#233)
* Mock `matchMedia`
* Expose label in `SettingsRow` component
* Add test to cover the case of changing PHP version
* Revert "Expose label in `SettingsRow` component"
This reverts commit bc37161.
* Update change PHP version test case
* Remove `getPhpVersion` hook and IPC handler (#239)
* Remove `getPhpVersion` hook and IPC handler
* Use `??` operator instead of `||` when setting the php version
* Add inline comment in Jest setup
The comment clarifies why we need the polyfill.
Related to: #231 (comment)
* Update `ContentTabSettings` unit tests
* Bump default PHP version to `8.1` (#240)
* Bump default PHP version to `8.1`
This change is driven by the fact that version `8.0` already reached its end-of-life by 2024.
https://www.php.net/supported-versions.php
* Address failure in `createSite` unit test
---------
Co-authored-by: Derek Blank <derekpblank@gmail.com>
Co-authored-by: Carlos Garcia <fluiddot@gmail.com>
0 commit comments