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
Prepare 1.6 release #317
Prepare 1.6 release #317
Conversation
Do not create_activity on an update action unless model is changed
Rails 5.1 compatibility for update action (for PR public-activity#290)
Adding license info to the Gemspec.
`base_class` in ActiveRecord returns `PublicActivity::ORM::ActiveRecord::Activity` incorrectly. Since `PublicActivity::ORM::ActiveRecord::Activity` is really an abstract class for all intents and purposes, it should be declared so that `base_class` returns `PublicActivity::Activity` instead. My use case was using the `unread` gem to track who had read an activity. It uses `base_class` to record the polymorphic type of the `readable` which is the Activity in this case. All the tests passed with this addition but I’ve added another to ensure that `base_class` returns the correct value.
`base_class` is an `ActiveRecord` method and doesn’t apply to other ORM’s.
…s-true Set self.abstract_class = true
Use rails_helper instead of spec_helper for disabling public_activity
Fix the readme, missing ')'
mongo-mapper gem relies on mongo 1.x but versions >= 1.10.0 started using upsert in a way that is incompatible with mongo 3.x
If you get Travis notifications and I just spammed the crap out of your mailbox then I apologize! Fixing those builds felt like this: I've made sure Travis is green now. @pokonski, anything else that is required before you can release 1.6 ? |
@pokonski Any chance you'll look at it or you're not interested in development anymore and it makes more sense to fork? :) (sorry for applying pressure but I need this release) |
Hey @d4rky-pl, for some reason I missed your PR! Let's get this released, then 😁 I could definitely use some active maintainers, and I'm open to get some help :) |
Hey there, @pokonski!
I know you're not using this library anymore and you are relying on community testing so I've upgraded this gem on a pretty big existing codebase that previously used 1.4 and ran it's test suite. Everything seems to be working fine (and it seems I'm not the only one that did it)!
I've merged the changes from 1-5-stable branch to this one and applied patch from #315 to make it work in our project. What else do you need to release 1.6?