expire_leaderboard_at effects on global_member_data

[c0d3c0mpil3]

Hi,
We have decided to use your awesome package to replace our postgres one. During the testing period, we have encountered an issue regarding time-based leaderboards. When I use expire_leaderboard_at on our leaderboard which uses global member data, it sets the same expiration date on the global member data too, which is not what we desire since other keys use this data too.
As I tracked the code, this method "_member_data_key" returns the member data key for "expire_leaderboard_at" which causes the global member data to be deleted.
Is there a workaround to prevent this behavior or is it in your plan to develop this feature?

[czarneckid]

There's currently no option for persistent member data. As a workaround, you could store member data in a separate Redis hash not managed by the leaderboard library.

[c0d3c0mpil3]

Sure, that came to my mine too but I thought implementing another method to get the user data key while setting expiration in global user data mode would be nice.
Thanks

[czarneckid]

It's not the member data key function I would change in this case, but maybe a feature around persisting member data to not expire the member data leaderboard.

[c0d3c0mpil3]

That would be great, thanks.