Do you need very strict Backwork Comapibility that prevents CI4 development?

Thanks all.

My example that changes method parameter from nullable to not nullable was bad.

?array $options = null → array $options = []

Because in fact, it does not break extended classes.
https://3v4l.org/OYbIf

In this case, if a user calls the method with null like map([...], null), it causes a fatal error.
But it seems nobody does like that.

---

At least, no one here objected to minor method signature changes in minor version up, e.g., 4.2.0.
The assumption is that we describe breaking changes clearly in the upgrade notes.

ci-phpunit-test | CodeIgniter Testing Guide | CodeIgniter 3 to 4 Upgrade Helper