Please prefix your outdated Composer Dependencies

  • Resolved Anonymous User 14808221

    (@anonymized-14808221)


    2 months, 1 week ago

    Hello, today I stumbled over the same issue as https://www.ads-software.com/support/topic/fatar-error-4/

    This issue will happen to anyone running a tad more modern plugins using Composer Dependencies that are not tailored to support outdated PHP versions.

    It is your choice to support those PHP versions, but I would kindly want to ask, please do not force anyone else to prefix their Composer Dependencies when they choose to not support those PHP versions.

    Instead, you should either prefix your dependencies or update them.

    Tools like php-scoper can help you with this. The thing is, if your plugin is installed on a website and anyone uses a newer PSR or else (monolog, etc etc) Dependency, then Fatal errors become the case. In my opinion it is not the task of the developer who choses modern versions to prefix their code. If compatibility is your main concern, I feel the task is on your end.

    Thank you!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Krystian from Syde

    (@inpsydekrystian)

    Hello @bedas

    Thank you for reaching out.

    We understand your concerns, and we plan to scope the plugin dependencies soon. However, there are several tasks that need to be completed beforehand, such as raising the minimum PHP version and introducing modularity. These changes are coming in the next update.

    As for the scoped plugin files, we estimate that they will be available in 2-3 updates.

    Kind Regards,

    Krystian

    Thread Starter Anonymous User 14808221

    (@anonymized-14808221)

    Hello @inpsydekrystian

    Thank you for the information!
    Happy you have this on your radar.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.