-
-
Notifications
You must be signed in to change notification settings - Fork 638
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
drop support for InheritedResource #370
drop support for InheritedResource #370
Conversation
…o feature/drop_support_for_inherited_resource # Conflicts: # CHANGELOG.rdoc
no, sorry. we don't support it anymore. I suggest you to monkey patch cancancan in your project, even if this can tie you to old, unsupported, libraries even more. |
Just as an FYI inherited_resources was transferred to the activeadmin organization for continuing maintenance about a month after this PR was merged. New features are discouraged but Rails 5.2 is supported. |
Hi @teohm, did you figure out a good upgrade path? I'm in a similar situation, upgrading to latest Rails and CanCanCan, only to discover that CanCanCan no longer works with InheritedResource (even though InheritedResource is still maintained and used). I guess I'll try copying the code that was in earlier version of CanCanCan and see if it still works... 😞 |
Fortunately there wasn't a very big integration layer...
|
A new gem is welcome, I don't feel ike adding it back to the source code. It has been eliminated because the project was abandoned. Now the project is maintained again but they also suggest not to use it so... |
I understand... :) A new gem is a good idea. |
Here is one: https://rubygems.org/gems/cancan-inherited_resources |
replaces https://github.com/CanCanCommunity/cancancan/pull/266/files since InheritedResource is not supported anymore. see: https://github.com/josevalim/inherited_resources#deprecation-notice