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
Fix right way #80
Fix right way #80
Conversation
This is the expected behavior, we want |
Example role security does not work:
|
Of course, there is no role for autocomplete, it's mapped on role required for list. Do you really need different role for autocomplete and list ? |
By default it takes the entity role, as in the example, but a minor role does not see a select autcomplete in a form. |
Autocomplete required role for |
If
Product Form uses autocomplete category and it works. If
Product Form uses autocomplete category and it works. |
So you want the same user cannot access list but is allowed for autocomplete ? This is not expected by the bundle and changing it is a BC break (existing projects do not define a specific role for Of course you can override |
If I treat the role 'autocomplete' only if it is defined in the yaml, otherwise I will use it as 'list'. |
It would be the good move, but required changes in the code seems important for a minor improvement (that can easily be obtained by overriding). |
right way:
http://php.net/manual/en/control-structures.switch.php
$actionName = 'automplete'
error: no break changes $actionName to 'list'