Dynamic Roles

Hey Farry7,

Basically, it's the same principle. But those terms are coming from Doctrine that is standalone library, Symfony just has integration for it. And also because entity is a bit more complex actually as it's used for ORM. About templates, well, view is a concept, but actually template is something that implements that concept I think. Anyway, template is much more understandable for more people than view I think. And it also comes from Twig template engine, it is called so (template engine), so it makes sense it works with templates :)

P.S. Btw, Symfony officially is not an MVC framework but Request-Response framework ;)

I hope this helps :)

Cheers!

Hey Dung,

Nope, unfortunately, I don't know any bundles for this. But actually we already use a library that implements this dropdown :) Twitter bootstrap is already handle a lot of useful code behind the scen that we can re-use. As developers, we just need to put proper HTML code with CSS classes to make it working and that's it. In case you want to make it even simplier - I'd recommend you to look into direction of Twig macros for example. you can add a few dropdowns, notice some code duplication and then refactor this code with Twig macros. Then just call those macros passing proper argument and macro will build the dropdown for you. But just avoid to overcomplecate things. Sometimes it's easier to just copy/paste some ready-to-use template from the Twitter Boostrap's docs page than overload your macros with many arguments. So, if you need one drowdown, creating a macro for this purpose is just an overkill as for me, easier to copy/paste the ready-to-use code from the docs :)

I hope this helps!

Cheers!

Hi victor
1) I actually ended up with just using standard Boostrap drop down html :) - they are clean and short
2) I appreciate you introduce Twig macros, I have seen it somewhere but never known what it is but now I do and I will learn it :)
Thanks for your insight.
Dung.

Hey Dung,

Yeah, probably the best solution! About macros, we have a Twig course, and we also talk about macros there as well, you may want to check it: https://symfonycasts.com/sc...

Glad it helped!

Cheers!

Thank you!

Hey Zesty

That's due a BC break between Symfony and latest PHP version. Here you can read more details about it: https://symfonycasts.com/sc...

Cheers!

Hey unionelein

At the moment there isn't any built-in feature for it, but here is a PR where you can find some workarounds: https://github.com/symfony/...

Cheers!

Hey Remus M.

That's weird, you should see a list of radio buttons because you activated the 'expanded' option. Can you show me a screenshot of how the form looks like? Also, give it a check to the html generated by the Form component, probably there might be a hint of what's going on.

Cheers!

registration form

upon submit ->

Expected argument of type "array", "string" given at property path "roles".

Ohhh of course! That's because your `roles` property expects an array and since you are selecting only one option you get in a string. I believe you will need a DataTransformer for this task.
You can find more information here: https://symfony.com/doc/cur...
Or you can watch how Ryan implement one here: https://symfonycasts.com/sc...

Cheers & Merry Christmas to you too (a bit late)!

I've come up with this so far

`
->add('roles',ChoiceType::class, [

'mapped' => false,
'expanded' => true,
'label' => 'Profile Type',
'choices' => [
    'User' => self::RUSER,
    'Agency' => self::RAGENCY,
            ],
'constraints' => [
    new NotBlank ([
        'message' => 'Choose a profile type !'
        ]),
    ]
])

`

it seems to work :)

I knew that it expects an array :) ( its more than obvious )

I don't know how to transform that field ...

Hey Ad F.!

This is an AWESOME question :), and you already understand the problem well. So, here are some options, depending on what you need:

1) The solution you posted above uses "mapped => false". That WILL work, but you will then need to read that data manually in the controller to set the string value from the ChoiceType, turn it into an array, and set on the object - e.g.

$user->setRoles(
    [$form['roles']->getData()]
);

This is not a fancy solution, but it should work.

2) More generally, we have "roles" set as an array in the database, because Symfony expects getRoles() to return an array. But if you have a simpler setup where you only ever assign one role, you could simplify this:

A) Change the roles property in User to role and make it a string
B) Add getRole() and setRole() methods
C) In getRoles(), just return your one role, wrapped in an array (and maybe also with ROLE_USER)
D) In your form, the field would just be called "role"

Let me know if that makes sense!

Cheers!

weaverryan

I'm not sure if you are still looking for this but here's my solution to the same problem of wanting the User Roles displayed as a single dropdown menu...

As Ryan ( weaverryan ) suggested I added a Data Transformer to my FormType class

Building my Admin Roles dropdown menu

`
$builder->
->add('roles', ChoiceType::class, [

'multiple' => false,
'label' => 'Set Account Role',
'choices'  => [
    'Please Select' => '',
    'User' => 'ROLE_USER',
    'Admin' => 'ROLE_ADMIN',
    'Super Admin' => 'ROLE_SUPER_ADMIN',
],

]);
`

And then the Data Transformer itself...

`

   $builder->get('roles')
        ->addModelTransformer(new CallbackTransformer(
           function ($rolesArray){
               if ($rolesArray) {
                   return count($rolesArray) ? $rolesArray[0] : null;
               }
           },
            function ($rolesString){
               return [$rolesString];
      }));

`

Worked a treat and no unmapping from the User entity needed.