Specifications for the Rails Assessment Specs:
X Using Ruby on Rails for the project
X Include at least one has_many relationship (x has_many y; e.g. User has_many Recipes) User has many Teams
X Include at least one belongs_to relationship (x belongs_to y; e.g. Post belongs_to User) Team belongs to User
X Include at least two has_many through relationships (x has_many y through z; e.g. Recipe has_many Items through Ingredients)
Team has many Players through PlayerTeams Player has many Users through Teams
X Include at least one many-to-many relationship (x has_many y through z, y has_many x through z; e.g. Recipe has_many Items through Ingredients, Item has_many Recipes through Ingredients)
User has many Players through Teams // Player has many Users through Teams
X 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 (attribute_name e.g. ingredients.quantity)
Player.captain
X Include reasonable validations for simple model objects (list of model objects with validations e.g. User, Recipe, Ingredient, Item)
Team, PlayerTeams
X Include a class level ActiveRecord scope method (model object & class method name and URL to see the working feature e.g. User.most_recipes URL: /users/most_recipes)
Player.get_guards (self.where("position LIKE ? ", "G")) X Include signup (how e.g. Devise)
Devise
X Include login (how e.g. Devise)
Devise
X Include logout (how e.g. Devise)
Devise
X Include third party signup/login (how e.g. Devise/OmniAuth)
Devise/OmniAuth
X Include nested resource show or index (URL e.g. users/2/recipes)
users/2/teams
X Include nested resource "new" form (URL e.g. recipes/1/ingredients/new)
users/1/teams/new
X Include form display of validation errors (form URL e.g. /recipes/new)
/teams
Confirm:
X The application is pretty DRY
X Limited logic in controllers
X Views use helper methods if appropriate
X Views use partials if appropriate