Specs:
- Using Ruby on Rails for the project -
Yup, Its using Rails - Include at least one has_many relationship (
User has many substitutions) - Include at least one belongs_to relationship (
Ingredient belongs_to Categoryamoung others) - Include at least two has_many through relationships (
has_many :ingredients, :through => :substitutions, :source => :sub and Category has many substitutions through Ingredients) - Include at least one many-to-many relationship (
has_many :ingredients, :through => :substitutions) - The "through" part of the has_many through includes at least one user submittable attribute, that is to say, some attribute other than its foreign keys that can be submitted by the app's user (
Substitution.description, .same_quantity and .issues attributes) - Include reasonable validations for simple model objects (
User, Substitution and Ingredients have validations) - Include a class level ActiveRecord scope method (
Substitution.last_5 - /substitutions/last_5) - Include signup (
Just using BCrpyt for password) - Include login (
Just using BCrypt/Session Controller) - Include logout (
Session Controller) - Include third party signup/login (
OmniAuth) - Include nested resource show or index (
/categories/1/ingredients/index) - Include nested resource "new" form (
/categories/1/ingredients/new) - Include form display of validation errors (
/categories/ingredients/_formandsubstitutions/_form)
Confirm:
- The application is pretty DRY
- Limited logic in controllers
- Views use helper methods if appropriate
- Views use partials if appropriate