Permalink
Commits on Nov 9, 2012
  1. Update CHANGELOG

    czarneckid committed Nov 9, 2012
  2. Removes `:with_scores` and `:with_ranks` as valid options

    * Removes `:with_scores` and `:with_ranks` as valid options.
    * `rake test_rubies` will only test under 1.8.7 and 1.9.3 now.
    * Update README for :sort_by option.
    * Update CHANGELOG.
    czarneckid committed Nov 9, 2012
Commits on Nov 8, 2012
  1. Bump version to 3.0.0.rc1

    czarneckid committed Nov 8, 2012
Commits on Oct 29, 2012
  1. Add a desc to the Rakefile

    czarneckid committed Oct 29, 2012
Commits on Oct 21, 2012
  1. Merge

    czarneckid committed Oct 21, 2012
  2. Version 3 proposal: Add a `:sort_by` option

    As indicated in #29, the currently undocumented behavior of a
    direct call to `ranked_in_list` is to do no sorting on the results.
    The call was originally intended to be used to retrieve a list
    of friends from a leaderboard. However, it would be useful in
    certain situations to have the results sorted. This adds a
    `:sort_by` option to that would be appropriate for the
    `ranked_in_list` call to sort by either score (`:score`) or
    rank (`:rank`) when returning results.
    czarneckid committed Oct 21, 2012
  3. Version 3 proposal: Add a `:sort_by` option

    As indicated in #29, the currently undocumented behavior of a
    direct call to `ranked_in_list` is to do no sorting on the results.
    The call was originally intended to be used to retrieve a list
    of friends from a leaderboard. However, it would be useful in
    certain situations to have the results sorted. This adds a
    `:sort_by` option to that would be appropriate for the
    `ranked_in_list` call to sort by either score (`:score`) or
    rank (`:rank`) when returning results.
    czarneckid committed Oct 21, 2012
Commits on Oct 12, 2012
  1. Version 2.5.0

    * Update README with example for `members_from_rank_range`
    * Update CHANGELOG.
    * Bump version to 2.5.0.
    czarneckid committed Oct 12, 2012
  2. Merge pull request #28 from agoragames/members-from-rank-range

    Members from rank range
    czarneckid committed Oct 12, 2012
  3. Add test for single member

    czarneckid committed Oct 12, 2012
  4. Retrieve members in a rank range

    * Added `members_from_rank_range` and `members_from_rank_range_in` methods.
    * Updated specs.
    czarneckid committed Oct 12, 2012
Commits on Sep 23, 2012
  1. Run the specs in random order

    czarneckid committed Sep 23, 2012
Commits on Sep 16, 2012
  1. Merge branch 'version-3-proposal-store-member-data-in-a-single-hash' …

    …of github.com:agoragames/leaderboard into version-3-proposal-store-member-data-in-a-single-hash
    czarneckid committed Sep 16, 2012
  2. Version 3 proposal: Store optional member data in a single hash

    This has the benefit of not using a separate hash for every single
    member's data. As is updated in the documentation, you can store
    more data for a given member by, for example, encoding a Hash
    in JSON. Not only will this save on Hash-splosion if using member
    data in a leaderboard, it also means that when deleting a
    leaderboard, we can also delete ALL of the member data at once. In
    version 2.x, if using member data, you would have to go through and
    delete the member data hashes individually. Yikes!
    czarneckid committed Sep 16, 2012
  3. Rebase from master

    czarneckid committed Sep 16, 2012
  4. Version 3 proposal: Remove use_zero_index_for_rank_option

    Is this ever really used in practice? My guess is no. Although it
    could be left in as it's not necessarily a lot of code, but it
    does remove some conditional paths.
    czarneckid committed Sep 16, 2012
  5. Version 3 proposal: Store optional member data in a single hash

    This has the benefit of not using a separate hash for every single
    member's data. As is updated in the documentation, you can store
    more data for a given member by, for example, encoding a Hash
    in JSON. Not only will this save on Hash-splosion if using member
    data in a leaderboard, it also means that when deleting a
    leaderboard, we can also delete ALL of the member data at once. In
    version 2.x, if using member data, you would have to go through and
    delete the member data hashes individually. Yikes!
    czarneckid committed Sep 16, 2012
  6. Version 3 proposal: Remove use_zero_index_for_rank_option

    Is this ever really used in practice? My guess is no. Although it
    could be left in as it's not necessarily a lot of code, but it
    does remove some conditional paths.
    czarneckid committed Sep 16, 2012
Commits on Aug 28, 2012
  1. Simplify Rakefile to no longer try and automatically start and stop R…

    …edis when running the specs
    czarneckid committed Aug 28, 2012
  2. Be better about inline URLs.

    czarneckid committed Aug 28, 2012
Commits on Aug 23, 2012
  1. Merge pull request #24 from agoragames/cleanup-ruby-warnings

    Cleanup Ruby warnings
    czarneckid committed Aug 23, 2012
  2. Cleanup Ruby warnings

    czarneckid committed Aug 23, 2012
Commits on Aug 3, 2012
  1. Fix spelling

    czarneckid committed Aug 3, 2012
Commits on Jul 30, 2012
Commits on Jul 27, 2012
  1. Merge pull request #21 from hypomodern/get_entire_leaderboard

    Get entire leaderboard
    czarneckid committed Jul 27, 2012
Commits on Jul 9, 2012
  1. Merge pull request #19 from agoragames/ttl

    Added expire_leaderboard and expire_leaderboard_at methods and specs.
    czarneckid committed Jul 9, 2012
Commits on Jul 8, 2012
Commits on Jun 25, 2012