lastomato / mongo_followable Goto Github PK

a follow b
a.follow_at(b) => Time ?

Thank you for a great gem.

I'm using your gem with models like "Post" and "ChildPost".
In this case, for inherited model name, rebuild_instances() fails for "ChildPost".

How about just call constantize() without capitalize() ?

Since scope :by_type also calls type.capitalize(), it fails for "ChildPost" again.

I'm using mongo_followable to handle not only following but favorites in my app. For both favorites and follow I use Mongoid::Observer to send notifications to users when each happens.

What I've found is it's kind of clunky. For example in order to send a notification to a User is being followed I do the following...

  def after_save(follow)
    if follow.f_type = "User" and follow.following_id_changed? and follow.following_id_was == nil
      followed = User.find(follow.f_id)
      followed.notify(:follow,
        actor: follow.following
      ) if followed
    end
  end

One thing that kind of threw me off was I wasn't sure why there are two follow documents? I thought it was for bidirectional following but it looks like when both users follow each other there are 4 documents.

The other thing I'm also wondering is if I could have favorites be in another collection. I feel like mixing them in one collection isn't optimal.

When A follow B, and then B is deleted.
There will be a mongoid document not found error when we call A.all_followees

if any follower found guilty of breaching conditions admin can able to block the specific user from group.....

The all_followers and all_followees methods seem very inefficient where there are lots of records, and since they return arrays they can't be paginated using standard Rails pagination gems.

if we use this for 'User follow User' scenario we may need confirmation before following. so can u please provide that?

I'm getting a stack level too deep error when using the all_followers and followers_count methods.