- Issue created by @mstrelan
- Merge request !5510Add declare(strict_types=1) to all Functional tests → (Closed) created by mstrelan
- 🇦🇺Australia mstrelan
mstrelan → changed the visibility of the branch 3399746-strict-types-functional-fix to hidden.
- 🇦🇺Australia mstrelan
The only remaining issue before this can be merged is 📌 Fix strict type errors in WebAssert calls Needs review .
- Status changed to Needs work
10 months ago 11:07am 27 February 2024 - 🇬🇧United Kingdom longwave UK
Agreed with @mstrelan that although we tried to fix all strict errors in 📌 Fix strict type errors in WebAssert calls Needs review one more has snuck in since; as it's only one instance the most pragmatic way to continue is just to apply that fix directly as part of this issue.
- Status changed to Needs review
10 months ago 11:42am 27 February 2024 - Status changed to RTBC
10 months ago 11:55pm 27 February 2024 - 🇦🇺Australia acbramley
Confirmed that the IS is correct, the MR only contains strict_types changes plus the 2 commits mentioned + the phpcs.xml.dist change (using
git diff --color-words 11.x | grep -v declare\(strict_types
and scanning the output)The line number changes make sense as we are adding 2 lines to those files.
These changes are the new fixes discussed above.
This is ready to go, nice!
-
longwave →
committed a23b6d67 on 10.3.x
Issue #3399746 by mstrelan, acbramley: Add declare(strict_types=1) to...
-
longwave →
committed a23b6d67 on 10.3.x
-
longwave →
committed e3fab520 on 11.x
Issue #3399746 by mstrelan, acbramley: Add declare(strict_types=1) to...
-
longwave →
committed e3fab520 on 11.x
- 🇬🇧United Kingdom longwave UK
Committed and pushed to 11.x and 10.3.x, thanks!
PHPStan crashed locally when running against this change via commit-code-check.sh with lots of "error code 127", unsure if there were too many changes for it to handle in one go?
- Status changed to Fixed
10 months ago 10:40am 28 February 2024 Automatically closed - issue fixed for 2 weeks with no activity.