Expose the row key names for custom naming schemes.

[seaders]

The naming scheme's doesn't fit the rest of our framework's system (a "member" will always be just a "uid", and the "member_data" is "userData" everywhere else), so they're now exposed to be customly overwritten via

Leaderboard.MEMBER_KEY = 'uid'

etc.

[czarneckid]

I'll integrate this over the next day. Thanks.

[seaders]

Cheers David, thank you for your great work on this library. I had started
writing our own leaderboard library and it was about a day (stupidly)
before I googled for something like this library and when I scanned this,
it was 1000% what I wanted compared to about the 5% of what I'd written
beforehand.

We only implemented the with_member_data bit today, so that's when I saw
that we'd much prefer to have things consistent with the rest of our
framework and made the pull request.

On Thu, Jan 23, 2014 at 1:05 AM, David Czarnecki
notifications@github.comwrote:

I'll integrate this over the next day. Thanks.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/18#issuecomment-33087569
.

[seaders]

Awesome, awesome, awesome. Thanks so much David, great library and it's always brilliant when open source maintainers are as quick to respond as you've been.

[czarneckid]

No problem. Available in 2.7.0, https://pypi.python.org/pypi/leaderboard.

Sorry it took slightly longer to release the latest code, but had to balance that with the Ruby and JavaScript leaderboard libraries. I may make a tweak to the Python library to allow for the key options to be set in the constructor, but that'll be in a patch update.