Hi!
I would like to know if the current implementation of RBAC is stable or just a port of V1.
For example, is $bizRule still being used?
And what about the table structures…
Are any plans to make big changes?
Hi!
I would like to know if the current implementation of RBAC is stable or just a port of V1.
For example, is $bizRule still being used?
And what about the table structures…
Are any plans to make big changes?
@zelenin thanks for your answer…
I’ve already read the documentatio and began to implement RBAC in a proyect, but my question is if it’s just a port of V1 RBAC and are any plan to make changes or it’s the definitive version…
I have been looking at it and it looks like a port of working code from V1
It is a port from 1.1. If you have any change suggestions, post at github.
Ok! But I will post here first so I don’t generate noise in github…
Just some comments…
[list=1]
[*]It is posible replace $bizRule evaluation for Closures?
[*]For DbManager, add integer for primary keys and make the current one just unique…
[/list]
No because rules could be stored in database.
What for?
[list=1]
[*]Well, I think this is a very old practice and have some drawbacks, like rules hard to debug and code readibility decrease…and maybe security…
[*]
[list=1]
[*]Readability. Convention…
[*]I know current one is a “correct” design and primary keys are well choosen…but it’s harder to develop a frontend always taking in count parent and child as strings. Think in URLS, for example…
[/list]
[/list]
This is the major enhancement we want to implement for RBAC before GA release: https://github.com/yiisoft/yii2/issues/499
Anyone wants to work on it? 
I wonder in practice (in YII) how needed is storing php code in database…
I would remove that entirely and would rely in closures if it’s needed…
And what about point #2?
I didn’t see that very long discussion…and see that you already saw some drawbacks…
Sadly, my skill level won’t allow to help in the development here… 