We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We can use kan not only roles and user. Also, same interface is good for working with permissions, experiments and etc.
That's why we can start use plugin system for helping use kan with other areas.
I have no idea how it should look like, but we can start discussion and find what the best way for this.
My general points around plugin system:
Also, we can move callbacks and notifications to plugins too
Kan::Plugin.register(:roles) { Kan::Plugin::Roles } Kan::Plugin.register(:custom) { CustomKanPlugin } class Post::Abilities include Kan::Abilities extend Kan::Plugin[:roles] register('read') { |_, _| true } register('edit') { |user, post| user.id == post.user_id } register('delete') { |_, _| false } end
The text was updated successfully, but these errors were encountered:
cc @IvanShamatov @apotonick
Sorry, something went wrong.
No branches or pull requests
We can use kan not only roles and user. Also, same interface is good for working with permissions, experiments and etc.
That's why we can start use plugin system for helping use kan with other areas.
I have no idea how it should look like, but we can start discussion and find what the best way for this.
My general points around plugin system:
Also, we can move callbacks and notifications to plugins too
API ideas
The text was updated successfully, but these errors were encountered: