Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Newer
Older
100644 56 lines (35 sloc) 2.654 kB
ca47151 @cmer Refactored to support multiple data stores
authored
1 # Changelog
2
7639e23 @cmer getting ready for 1.1.0 release
authored
3 ## 1.0.1 (January 8, 2014)
4
3e904fc @cmer giving credit where credit is due
authored
5 * Supports Rails 4 (thanks @thomas88)
7639e23 @cmer getting ready for 1.1.0 release
authored
6 * Dropping official support for Ruby 1.8.x, 1.9.2.
fafd54e @cmer drop support for 1.8.x
authored
7
8
7567edc @cmer Fuck it, let's release this motherfucker. It's been in perpetual Gmai…
authored
9 ## 1.0.0 (May 29, 2013)
10
11 * Same as 0.5.0.beta4. Been using it in a very high traffic production environment for over a year and it works.
12
a128d14 @cmer preparing 0.5.0.beta release
authored
13 ## 0.5.0.beta (June 6, 2012)
ca47151 @cmer Refactored to support multiple data stores
authored
14
268041f @cmer Updated changelog to reflect _relation methods
authored
15 * **IMPORTANT:** This release includes many changes, some breaking. Make sure to test your code carefully after upgrading.
694228e @cmer Renamed store classes
authored
16 * **BREAKING CHANGE:** Your Like, Follow and Mention models should now inherit the Socialization store base class instead of using the acts_as helper. (e.g.: class Follow < Socialization::ActiveRecordStores::Follow). See demo app for an example.
268041f @cmer Updated changelog to reflect _relation methods
authored
17 * **BREAKING CHANGE:** the `followers`, `followables` etc methods now return an array of objects. Use methods such as `followers_relation` for an ActiveRecord::Relation.
8403800 @cmer mentioned Redis in changelog
authored
18 * Changed: The persistence logic has now been moved to the Socialization::ActiveRecordStores namespace. More stores can be easily added.
ca47151 @cmer Refactored to support multiple data stores
authored
19 * Changed: `like!`, `follow!`, and `mention!` now return a boolean. True when the action was successful, false when it wasn't (e.g.: the relationship already exists).
20 * Changed: `unlike!`, `unfollow!` and `unmention!` will now return false if there is no record to destroy rather than raising `ActiveRecord::RecordNotFound`.
21 * Changed: Records can now like, follow or mention themselves. If you want to prevent this, it should be enforced directly in your application.
268041f @cmer Updated changelog to reflect _relation methods
authored
22 * Added: Data can now be stored in Redis.
ca47151 @cmer Refactored to support multiple data stores
authored
23 * Added: `toggle_like!`, `toggle_follow!` and `toggle_mention!` methods. Thanks to [@balvig](https://github.com/balvig).
24 * Added: support for single table inheritance. Thanks to [@balvig](https://github.com/balvig).
9e574e2 @cmer Now raises Socialization::ArgumentError instead of ::ArgumentError
authored
25 * Changed: raises Socialization::ArgumentError instead of ::ArgumentError
ca47151 @cmer Refactored to support multiple data stores
authored
26
27 ## v0.4.0 (February 25, 2012)
28
29 * **BREAKING CHANGE:** Renamed `mentionner` to `mentioner`. This is proper English.
30 * Added: `followees`, `likees` and `mentionees` methods to `Follower`, `Liker` and `Mentioner`. Thanks to [@ihara2525](https://github.com/ihara2525).
31
32 ## v0.3.0 (February 22, 2012)
33
34 * **BREAKING CHANGE:** `likers`, `followers` now return a scope instead of an array. They also require to have the class of the desired scope as an argument. For example: `Movie.find(1).followers(User)`.
35 * Added: Mention support.
36 * Some refactoring and clean up. Thanks to [@tilsammans](https://github.com/tilsammans)
37
38
39 ## 0.2.2 (January 15, 2012)
40
41 * Improved tests.
42 * Changed: Can no longer like or follow yourself.
43
44 ## 0.2.1 (January 15, 2012)
45
46 * Bug fixes
47
48 ## 0.2.0 (January 15, 2012)
49
50 * Bug fixes
51 * Made Ruby 1.8.7 compatible
52
53 ## 0.1.0 (January 14, 2012)
54
fafd54e @cmer drop support for 1.8.x
authored
55 * Initial release
Something went wrong with that request. Please try again.