-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[RFC] Cleaner separation between Sylius and Sylius-Standard #9305
Comments
Apart of them being useful in Sylius-Standard, we also need them to test the whole application using Behat. I'm not sure if I understand Symfony Flex issue correctly, but it's mostly connected to single bundles, not the whole application, so this should be possible just by customising them. |
@pamil Continuing the discussion here. We could start by getting rid of the shared |
The test app should have its own |
Also, all the Say, normally these issues would be fixed in Sylius-Standard, not Sylius: |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions. |
It's still a pain point from maintainer/contributor perspective. |
Even though we will probably be thinking about what we should do with Sylius-Standard in the future, I believe this issue can be closed 🖖 |
Currently, many files exist in the Sylius repository that are only useful for the Sylius-Standard repository. This means the two projects are tightly coupled in a convoluted way. Issues like #9301 and #9304 cannot be properly fixed, because of the lack of a clean separation. Of course, this also makes it almost impossible to move to Symfony Flex (correct me if I'm wrong).
The text was updated successfully, but these errors were encountered: