composer-patches VS Sylius

if you're using composer with joomla, and the plugin is installed via composer, you can commission someone to make the necessary changes, create a git diff patch that encapsulates the changes, then leverage cweagans/composer-patches to make it work. if/when new changes are necessary, they can build a new patch.

I've had problems with libraries using final having an API that isn't customizable enough in a particular way I need because I'm innovating in some way they could never have considered in the past, so my choice ends up either needing to fork the library or monkey patch it with https://github.com/cweagans/composer-patches so I can get rid of final so I can keep using it. They wouldn't accept a change in API or behaviour because it would break things for other users, etc.

There are cool tools to integrate patches from drupal.org (or your own custom patches) into your composer managed drupal website. For example (not drupal specific but works well with drupal+composer): https://github.com/cweagans/composer-patches

If the PR get's merged, I want `yay` or `pacman` to skip the patch. Ideally it would be declared in a pacman.patches file or similar to what https://github.com/cweagans/composer-patches provides for composer PHP package managment.

This has been an issue for a while, and is outlined here: - https://github.com/cweagans/composer-patches/issues/172#issuecomment-587147692 - https://github.com/cweagans/composer-patches/issues/326

Install a package that allows the composer to work with patches:

And if for some reason you do not want to make a fork, you can also create a composer patch with the help of https://github.com/cweagans/composer-patches

https://github.com/cweagans/composer-patches - this lets you patch packages when they are pulled in by Composer. I have used it in the past to get minor bugfixes into a project ASAP without having to wait for upstream or forking the entire package.

I think it would be difficult (or much harder) to build something like Sylius on top of Laravel. Especially if you want good code-coverage by tests.

For the development of high-scaling applications and responsive websites, open source headless commerce architecture has become the go-to option in recent years because of its flexibility, scalability, and agility. However, choosing the best open source headless ecommerce platform can be challenging. To help you navigate this complex landscape, this article compares two popular open source solutions: Medusa and Sylius.

Checkout Sylius. Try to run it and modify it in some way. Pretty big codebase and project. If you can modify it without directly rewriting the Syius code (like overloading Symfony services and so on...) you can be confident in your skills.

Can you tell me what exactly is wrong in language with code like this? Do note that this is still old <7.4 version, and version 8.0 and 8.1 gave us many goodies like constructor promotion, match, enums, throw expressions...

Just go with Shopify/Vercel. I've been hearing nice things about https://sylius.com/ too.

Sylius: https://sylius.com/

I would say Sylius is your best bet: https://github.com/Sylius/Sylius but I am sure there are many more.

Take a look at this: https://sylius.com/ it's opensource, based on Symfony and might be better than everything you mentioned.

Not sure what your needs are but yes I would use a framework and since you mentioned e-commerce I would take a look at this: https://github.com/Sylius/Sylius