I have users’ table users, where I store information like post_count and so on. I want to have ~50 badges and it is going to be even more than that in future.
So, I want to have a page where member of website could go and take the badge, not automatically give him it like in SO. And after he clicks a button called smth like “Take ‘Made 10 posts’ badge” the system checks if he has posted 10 posts and doesn’t have this badge already, and if it’s ok, give him the badge and insert into the new table the badge’s id and user_id that member couldn’t take it twice.
But I have so many badges, so do I really need to put so many if’s to check for all badges? What would be your suggestion on this? How can I make it more optimal if it’s even possible?
Thank you.
optimal would be IMHO the the following:
have an object for the user with functions that return user specific attributes/metrics that you initialise with the proper user id (you probably wanna make this a singleton/static for some elements…):
have a badge object that is initialised with an id/key and loads dependencies from your database:
then you could have a class that controls the awarding of batches (you can also do it inside user…)
and checks dependencies and prints failed dependencies etc…
you can extend to this class if you have very custom batches that require weird calculations.
hope i brought you on the right track.
untested andp robably full of syntax errors.
welcome to the world of object oriented programming. still wanna do this?