Sonataadminbundle: Suggestion: put "Form" classes into a separate library

[vyshkant]

My suggestion is to put some of the classes for working with forms into a separate library.

For example, in my project I'm going to create some (non-admin) filterable and sortable view of my entities. Following this goal, I will have to create my own classes like Sonata\AdminBundle\Form\Type\ModelType, Sonata\AdminBundle\Form\DataTransformer\ModelsToArrayTransformer, etc, and then use them to build forms.

My idea is to create reusable classes (a separate library, like Symfony "component") that can be used in SonataAdminBundle and beyond.

[core23]

We could move some Form's of the CoreBundle too (https://github.com/sonata-project/dev-kit/issues/348)

[kunicmarko20]

Also, there is a CollectionType Form in AdminBundle and in CoreBundle, so one of those could get a rename.

[stale[bot]]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[VincentLanglet]

There is now https://github.com/sonata-project/form-extensions, right time to move some forms ?

[core23]

Not sure if we should move ModelType and the other form types, because they are too admin specific

[VincentLanglet]

Not sure if we should move ModelType and the other form types, because they are too admin specific

The issue is old. Let's close this and see if mutiple contributors are asking for it ; which I doubt.