Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set proper requirement versions #54

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

JKetelaar
Copy link

This way you avoid having to update your composer.json every single release of your dependencies, without really being in danger of having incompatible versions.

The PHP version is simply the recommended version for every Magento 2 site.

This way you avoid having to update your composer.json every single release of your dependencies, without really being in danger of having incompatible versions.

The PHP version is simply the recommended version for every Magento 2 site.
@hostep
Copy link

hostep commented Mar 15, 2020

Magento 2.3.4 is compatible with up to PHP 7.3.x, just saying.

Honestly, you could test the code with something like https://github.com/PHPCompatibility/PHPCompatibility/ and then declare all the PHP versions which the tool is not complaining about. In this case you can probably already include PHP 7.4 as well even if no Magento version is out there which officially supports it yet.

@JKetelaar
Copy link
Author

There needs to be some backwards compatibility

@JKetelaar
Copy link
Author

And this change allows php 7.0+ with some restrictions on php 7.0 minor versions

@hostep
Copy link

hostep commented Mar 15, 2020

Ah sorry, I didn't notice you used ^7.1.0, I though it was ~7.1.0. My bad!

I don't like ^7.1.0 or >=7.0.13 though, because you can't know if the code will be 100% compatible with PHP 7.5 (which probably will not be released, but who knows).

@JKetelaar
Copy link
Author

If you don’t do this, then the developers need to update this on each release. And knowing the magento community (including this extension apparently), this doesn’t happen as often. So I’d rather be safe on that side, than wait for developers to update the compose.json, even if the code still might work.

I do agree with you though if the extension was daily/weekly maintained.

@JKetelaar
Copy link
Author

@dpdplugin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants