Skip to content

Support for new upcoming Symfony versions 3.3 and 4 #309

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

Closed
TheCelavi opened this issue Apr 11, 2017 · 6 comments
Closed

Support for new upcoming Symfony versions 3.3 and 4 #309

TheCelavi opened this issue Apr 11, 2017 · 6 comments

Comments

@TheCelavi
Copy link
Contributor

Hello,

New SF versions are about to come very soon. With those versions, there will be support for bundleless applications. Twig 2 is also released.

This project seams to have little activity lately. So, what is the plan for future support? Is there going to be continuation of further development of this bundle?

@bobvandevijver
Copy link
Member

Same as with the FormExtensionsbundle I'm afraid..

(for others, see symfony2admingenerator/FormExtensionsBundle#77)

@TheCelavi
Copy link
Contributor Author

Hm.... too bad, project is much better then SonataAdminBundle, per example... I have worked with both admin generators, Sonata is not nearly easily customizable as this one... but Sonata seams to have more "advertising" efforts invested in it...

Ok, so, it would be too bad to leave this project to die. How can we help? How about to start discussion on how to implement support for SF 3.3 / SF 4?

@bobvandevijver
Copy link
Member

When I read the articles about SF4, it seems like there is only a best practice to use bundle-less applications, but I guess that the original bundle structure would still be functional (but it might be I'm wrong).

Guess that if we want to support actual bundle-less applications, we should completely revisit the generation structure. That might be a cumbersome task...

@TheCelavi
Copy link
Contributor Author

Yes, it will be a lot of work to do. In order for this project to still be in the game is to support new, upcoming changes.

New improvements are required as well, such as speed of code generation, some optimizations and what now... Maybe even some feature depreciations, like support for Propel?

I am going to close this issue for now - just note that I am willing to help with working/maintaining this project.

@ioleo
Copy link
Member

ioleo commented Apr 12, 2017

@bobvandevijver is Propel currently maintained by anyone from the core team? while Doctrine ORM/ODM APIs have much in common and it's not a big leap to support the latter, Propel is whole diffrent game

I'd seriously consider @TheCelavi proposition of feature deprecation, if this bundle is to move forward.

@bobvandevijver
Copy link
Member

I believe only @cedriclombardot is using propel, and it looks like he's working on Propel 2 support (#307).

However, I would not mind dropping support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants