-
-
Notifications
You must be signed in to change notification settings - Fork 756
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
Move to Symfony Flex #5747
Comments
Yes we would like to move on Symfony Flex. However I'm wondering if it would be easy to do so without starting a new codebase from scratch; deprecations include, among other things, the rewrite of the user management part as FOSUserBundle is not compatible with Symfony 4+ |
If it can help, I made draft PR a few months ago but I abandoned them: |
Great! here a very big picture roadmap I can work on:
what do you think @Kdecherf ? |
from linked PRs:
@Kdecherf I assume this is abandonned? or is it still something you plan to work one? |
Of course we would like to move to Flex. |
Sure! meanwhile 2.5.0 get realease, I'll work on preparation work, the depreciations |
Looks good 👍 |
I'm currently working on removing depreciations from Wallabag codebase, so that we can upgrade to newer Symfony.
One big step in Symfony projects in Symfony Flex, that propose new way of managing dependencies, and a newer more standard project structure.
But one of the most impactful change is to not use bundles for application code.
Is migrating to Symfony Flex something you may considere to have a project structure aligned with Symfony recommendation?
If yes, I can work on doing this in multiple steps, the first ones beig to have just one bundle, so migrate in a clean way content of all bundles inside CoreBundle, preserving the separation with namespace.
The text was updated successfully, but these errors were encountered: