search

zendframework / zend-stdlib

Stdlib component from Zend Framework
BSD 3-Clause "New" or "Revised" License
384 stars 76 forks source link

[ERROR] Update ArrayObject.php in 2.7.7 #101

Closed Blaztix closed 5 years ago

Blaztix commented 5 years ago

Provide a narrative description of what you are trying to accomplish:

michalbundyra commented 5 years ago

@Blaztix Unfortunately zend-stdlib v2 is no longer supported. Please see: https://framework.zend.com/long-term-support for details.

Here you can see the hotfix to version 3: https://github.com/zendframework/zend-stdlib/pull/91

Blaztix commented 5 years ago

This is ridiculous, I'm not going to update a complete platform because a pull request can not be accepted....

I am an simple user running composer install and gets errors.... unacceptable

Ocramius commented 5 years ago

That's what you will get with any older release of a library. Upgrading is the correct resolution path: otherwise, run an older PHP version.

On Mon, Jul 8, 2019, 20:44 Blaztix notifications@github.com wrote:

This is ridiculous, I'm not going to update a complete platform because a pull request can not be accepted....

  • Add and restriction for PHP version or
  • Just add a literal 2 or replace with break and release a 2.7.8 or hotfix

I am an simple user running composer install and gets errors.... unacceptable

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/zendframework/zend-stdlib/pull/101?email_source=notifications&email_token=AABFVEBQ5P6OCJKMQUU6CUTP6ODIFA5CNFSM4H65RP4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZN726Y#issuecomment-509345147, or mute the thread https://github.com/notifications/unsubscribe-auth/AABFVEAFBY5FHRPYJFQMKXTP6ODIFANCNFSM4H65RP4A .

YetiCGN commented 5 years ago

Oh, I see that this has already been addressed. I just came across the same problem and will continue to use my fork of zend-stdlib 2.7.7 with the fix applied.

@Blaztix You can do the same, just add the forked repository in your composer.json and add or change the following line:

"zendframework/zend-stdlib": "dev-release-2.7 as 2.7.8",
YetiCGN commented 5 years ago

That's what you will get with any older release of a library. Upgrading is the correct resolution path: otherwise, run an older PHP version.

While I understand the rationale behind that and why making an exception for this one-line fix would call upon all sorts of "small fixes" for an outdated version, what people will really do is a) silence the warning or b) use a fork (like I do) with the patch applied.

Actually this is more a problem of Apigility claiming compatibility with php: ^5.6 || ^7.0 but not really being tested on 7.3 and 7.4. So people are finding out late in the testing process (like I did) when they likely already have switched to PHP 7.3 what with the accelerated release cycle of PHP. And then it's just a nuisance that can be silenced pretty easily. So no. I will not invest countless days into upgrading this legacy project to a newer version of Zend Framework.

Symfony forever!!! 😛