Hello,

Thanks for reporting this issue!
Ping @PrestaShop/prestashop-core-developers : Could someone please try to reproduce the issue, it's too technical!

Thanks in advance!

Hello @leemyongpakvn I think it's a great idea 👍

In a module, we cannot mark "this module is NOT compatible with PHP {...}" (we can mark it in composer.json but it will not be scanned by PrestaShop) however we can mark "this module compatibility range is {...} to {...}"

As each Core version has a dedicated PHP range, it follows.

For example if you say the module minimum Core version is 1.7.7, as 1.7.7 min PHP version is 7.1 then it can be understood as "the module minimum PHP version is 7.1"

I love this idea, but to be sure let me ask the opinion of @PrestaShop/committers

Indeed, I have already gone through modules in php 5.4 and with older versions of phpstan.
I also think there is work to be done on php versions and some dependencies in modules.

The PHP version of the modules must follow the PHP version of prestashop, taking into account their compatibility range.

I like the idea.

@matks I chose PHP 7.1.3 and PS 1.7.7 because of this composer.json.
Furthermore, I suggest removing

    "platform": {
      "php": "5.6"
    }

from module's composer.json. That way, we can keep support for PHP 7.1.3 and PS 1.7.7 in production environment (merchants won't be shocked ;), while allow devs using php-dev-tools v4 and php-cs-fixer v3 (those require PHP 7.2) in development environment.

@leemyongpakvn, it seems to be a good idea to me for PHP 7.1 instead of oldies versions.

@leemyongpakvn yes, that's a good idea, because if you have platform requirement composer will throw you a warning if you don't meet requirements, so if we have:

   "platform": {
      "php": "5.6"
    }

and you, for example, generate autoloader, i'll check whether the version of PHP is correct

Idea approved 👍 and I change the labels: it's not a Bug it's a Feature

Full list: