Skip to content

Latest commit

 

History

History
25 lines (23 loc) · 2.28 KB

spec.md

File metadata and controls

25 lines (23 loc) · 2.28 KB

Specifications for the Rails Assessment

Specs:

  • Using Ruby on Rails for the project
  • Include at least one has_many relationship (x has_many y; e.g. User has_many Recipes). User has_many Remedies.
  • Include at least one belongs_to relationship (x belongs_to y; e.g. Post belongs_to User). Remedy belongs_to User.
  • Include at least two has_many through relationships (x has_many y through z; e.g. Recipe has_many Items through Ingredients). User has_many Comments through Remedies. Remedy has_many Categories through Remedy_Categories. Category has_many Remedies through Remedy_Categories.
  • 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). Remedy has_many Categories through Remedy_Categories. Category has_many Remedies through Remedy_Categories.
  • 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) Comments have content.
  • Include reasonable validations for simple model objects (list of model objects with validations e.g. User, Recipe, Ingredient, Item) User, Remedy, Category, Comment.
  • 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) Users.elderly URL: /users/elderly
  • Include signup (how e.g. Devise) URL: /users/new
  • Include login (how e.g. Devise) URL: /signin
  • Include logout (how e.g. Devise) Logout link on users show page.
  • Include third party signup/login (how e.g. Devise/OmniAuth) Github
  • Include nested resource show or index (URL e.g. users/2/recipes) URL: /users/2/remedies and URL: /users/2/remedies/:id
  • Include nested resource "new" form (URL e.g. recipes/1/ingredients/new) URL: /users/2/remedies/new
  • Include form display of validation errors (form URL e.g. /recipes/new) Included display validation errors for all new views.

Confirm:

  • The application is pretty DRY
  • Limited logic in controllers
  • Views use helper methods if appropriate
  • Views use partials if appropriate