-
-
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
Symfony 7 support #15481
Comments
I don't intend on making the 3.x branch compatible with Symfony 7; generally, I keep my Symfony bundles compatible with two LTS' and the next major (3.x supports Symfony 4.4, 5.4, and 6.x; 4.x will support Symfony 5.4, 6.4, and 7.x). So, Sylius will need to upgrade to PagerfantaBundle 4.0 for Symfony 7 support. In good news, the 3.x to 4.x upgrade is much lighter this time around compared to the 3.x releases which had all sorts of internal refactoring and cleanup. |
thx @mbabker for all your work on external packages. |
Hi, |
FOSRestBundle is released with Symfony 7 support aslong as you don't use the SensioExtraBundle features. Thx to @mbabker |
Ok that means that we are now ready to work on technical packages 🎉 |
Payum is also ready on master branch, @lchrusciel @diimpp are you ready to rumble? |
Does this mean that you're going to convert all models/entities to use PHP attributes? That would be great because right now Sylius entities (which for some reason you call models) are very confusing given that the Maker Bundle creates entities with attributes by default (which I like - I really don't like the comments or XML approaches), while it seems that Sylius uses another approach (not sure if it uses comments or XML configurations or both - I've seen everything and nothing), which is confusing to me. Also, could someone tell me which Maker Bundle version I should use, so that I create entities which are compatible with Sylius? Version |
Hi @nbro,
|
@jakubtobiasz Thanks for the answer. My However, I had created my local Sylius application with |
@nbro Updated Sylius Standard wasn't available at day 0 of Sylius 1.13 release. So, despite you've got Sylius 1.13 installed (as a constraint was probably met), the configuration was from 1.12 times :). You can always try to run this command once again and check whether it works :). |
ThemeBundle is done :) |
| Q | A |-----------------|----- | Branch? | symfony-7 | Bug fix? | no | New feature? | no | BC breaks? | no | Deprecations? | no<!-- don't forget to update the UPGRADE-*.md file --> | Related tickets | mentioned in #15481 | License | MIT <!-- - Bug fixes must be submitted against the 1.13 branch - Features and deprecations must be submitted against the 1.14 branch - Features, removing deprecations and BC breaks must be submitted against the 2.0 branch - Make sure that the correct base branch is set To be sure you are not breaking any Backward Compatibilities, check the documentation: https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html -->
Final steps
Internal Components
Internal Bundles
Internal PRs
Sylius technical packages
External Packages
The text was updated successfully, but these errors were encountered: