-
Notifications
You must be signed in to change notification settings - Fork 197
Home
Badges data is stored in config/initializers/merit.rb
using ambry. Ambry is ActiveModel compliant, so it has very few differences to a "normal" ActiveRecord relation.
For instance, calling badges
on an object will return an Ambry::Mapper
, over which you may call each
as with any array, or just convert it to an array with to_a
(user.badges.to_a
).
If badges are stored in a DB table, and app is deployed without synchronizing the badges data with the server's, it will raise an exception for badge not found, or methods called from merit
on nil
. Having the app rely on DB entries makes it weak and error prone. badges
table would have to be exactly the same for all developers/instances of the app, which is awckward.
Badges tend to be a stable piece of information, and, as the app's stability depend on it, makes much more sense to have that data in code, sourced controlled. If you change merit rules badges you are changing code, and so you change badges data there as well.
ambry is a small library which provides a nice interface to the store of this kind of objects, which are not code but neither harmless data. It also provides validations and nice filtering syntax.