I think the main headache will be there : https://github.com/sonata-project/SonataAdminBundle/pull/1971 . The schema is a collection of definitions, and definition options are a collection too. Sonata doesn't play well with nested collection widgets ATM. I ended up creating 5 definition fields in my Library entity to avoid the first level (I know, it's very ugly :stuck_out_tongue_winking_eye: ).
I think the main headache will be there : https://github.com/sonata-project/SonataAdminBundle/pull/1971 . The schema is a collection of definitions, and definition options are a collection too. Sonata doesn't play well with nested collection widgets ATM. I ended up creating 5 definition fields in my Library entity to avoid the first level (I know, it's very ugly :stuck_out_tongue_winking_eye: ).