You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ended up not using Canard for a recent project because the "additive" nature of abilities does not include guest abilities.
I think the behavior should be, for example: guest, user, manager, admin
Instead it is: user, manager, admin
So any abilities defined for guest have to be duplicated in user. Not very DRY. While I realize this is a breaking change, to be perfectly honest, I can't think of any real world examples where a user would be denied from doing something that a guest can do.
The text was updated successfully, but these errors were encountered:
Signup and signin pages spring to mind. But point taken. I would consider adding it as a configuration option, but wouldn't want to trade potential DRYness for flexibility. Out of 5 projects I'm using Canard in only 1 would benefit from this. So I see the potential but not at the expense of a limitation. How about;
I ended up not using Canard for a recent project because the "additive" nature of abilities does not include guest abilities.
I think the behavior should be, for example: guest, user, manager, admin
Instead it is: user, manager, admin
So any abilities defined for guest have to be duplicated in user. Not very DRY. While I realize this is a breaking change, to be perfectly honest, I can't think of any real world examples where a user would be denied from doing something that a guest can do.
The text was updated successfully, but these errors were encountered: