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
In my work project we implement the json_decode method and it seems there is a method signature change between 2.2.2 and 2.2.3 which breaks our codebase.
I am curious why the method params would be changed outside of a major release in-line with Semver. https://semver.org/
If this is an intentional change, then I would recommend some documentation around it, as stipulating a Composer constraint of ^2.0 and implementing the class with a pre 2.2.3 release, when using composer update the code will break.
In my work project we implement the
json_decode
method and it seems there is a method signature change between2.2.2
and2.2.3
which breaks our codebase.I am curious why the method params would be changed outside of a major release in-line with Semver. https://semver.org/
If this is an intentional change, then I would recommend some documentation around it, as stipulating a Composer constraint of
^2.0
and implementing the class with a pre2.2.3
release, when usingcomposer update
the code will break.https://getcomposer.org/doc/articles/versions.md#caret-version-range-
The intention of this constraint is that updates should be safe.
The text was updated successfully, but these errors were encountered: