Feature Request: Ability to add other fields to badge definition

[rmccown]

Howdy
I'd like to request the ability to add other optional fields to the badge definition in the merit.rb file. Something like this:

Merit::Badge.create!({
:id=> 7,
:name=>'6 Months Active',
:image=>'badges/6months.png',
:description=>'Users that are active after six months',
:my_other_field=>"foo",
:my_other_field2=>"bar"
})

etc...

[tute]

This was discussed in: #28 (comment)

May I ask how would you use custom fields?

[rmccown]

A couple of ways. Our app will probably end up with fifty or more badges a user can earn. We'd like the ability to group them, sort them, and make them visible/active or not. So initially we have discussed needing:

:order=>
:group=>
:visible=>

flags. Granted, I could make my own badge_attribute table and link it over to Merit::Badge by badge ID, but that's not really clean.

Thanks
-=Bob

[tute]

I'm thinking of getting rid of the level attribute. I'm interested in your thoughts of that. If you wouldn't use it as merit intends right now, you may use it as 'group'.

I'll think about the other ones.

[rmccown]

We're not currently using level, and anything that needs a different level of activity, we're tracking ourselves (log-ins,score, etc). Maybe sub-classing ourselves is the right way to go about this

[tute]

Merit::Badge uses ambry, and ambry allows hashes as attributes. In that case, a custom_fields_hash (or similarly named) attribute in the Badge model would allow applications to extend badges however they want. PRs welcome. :-)

[rmccown]

Yes, a custom fields hash would be a great way to do it.