complete GameNight specs and associations #46
Conversation
| belongs_to :organizer, class_name: :User, foreign_key: :organizer_id | ||
|
|
||
| has_many :user_game_night_attendees | ||
| has_many :users, through: :user_game_night_attendees |
There was a problem hiding this comment.
@enriikke you'd mentioned the possibility of making these more generic (like Memberships in the case of Groups). What would that look like? Here, our UserGameNightAttendees has a user_id and a game_night_id. If you wanted something more versatile would you just have attributes like id_1 and id_2 so that a Membership or Attendance could apply to any type of model?
There was a problem hiding this comment.
Hey @npauzenga, making Membership or Attendance more generic would make it easier if we need to reutilize that same functionality. If we don't have a case where we would need to reutilize it then keeping them specific works great 😄.
If we wanted to generalize them, we could use polymorphic associations 👻 🐍. These shapeshifting creatures are documented here. ActiveRecord can handle everything for us but on a high level, all it's doing is adding two attributes to the table: an id and a type. We tell AR the name of our polymorphic friend, for example attendable and it uses that to add the column attendable_id, then it automatically figures out the type of object based on its class name and uses that for the attendable_type column. So when we query for user.attendances it's checking something like:
# This is probably not exactly how AR's implementation looks
Attendance.where(attendable_id: user.id, attendable_type: user.class.name.downcase)
|
Awesome work @npauzenga!!! |
complete GameNight specs and associations
Hey @enriikke one small question below...