For your Ironhack final project, you have 2 weeks to develop an idea of your choice. You will present your final project at the Hackshow.
This document contains all the relevant information pertaining to the final project phase of the course. Let's start with some basic facts to keep in mind.
This was a question from @photonerddan during class, and after looking through many examples online approaching it from an inheritance stance, as well as ones with examples that seemed outside of common use-cases, Mike and I decided to approach it from a problem / solution standpoint, which looks at it from a database perspective.
We will cover it more in-depth during the second week of Rails MakerSquare, but for now here is a short example to highlight the problem that polymorphism is solving in your database.
So let's start with the problem it is solving:
Polymorphism keeps you from having excessive foreign key columns in a database table where multiple things, such as notification feed items, are owned by other objects.
| <!-- app/views/devise/omniauth/link_user.html.erb --> | |
| <h2>Link your account</h2> | |
| <%= form_for(@user, :url => user_omniauth_link_url, :html => { :method => :put }) do |f| %> | |
| <p>You already have an account, that was created with email and password. To link your Facebook account, please enter your password. If you can't remember your password, you can recover it by clicking the link below.</p> | |
| <%= render "devise/shared/error_messages" %> | |
| <div> |