Feature proposal #3788
Updated by krileon about 7 years ago
Implement buttons that like, dislike, or share the ability to like another asset. The base for this stream api should be the follow class. There should only need to be 2 endpoints. 1 for displaying the button(s) (which also includes the ajax) current post. Like and 1 for saving the stream. When creating dislike will have counters going up as a likes stream the asset supplied post is the asset to liked/disliked. Likes and dislikes will be liked. For the button display endpoint it's probably best stored to reserve show/default for an actual view (e.g. if in the future there's a view separate DB table linking activity ID to display all the assets the it, user liked) so use ->likes( 'button' ) instead. A database table needs to be added to handle the storage who liked/disliked, status of the likes like/dislike (for now 1 or 0), and a table for storage date of the various like/dislike. They'll be toggle so you can like buttons (e.g. just like Locations, Actions, etc..). then unlike or dislike then undislike.