Skip to content

Latest commit

 

History

History
24 lines (22 loc) · 2.27 KB

spec.md

File metadata and controls

24 lines (22 loc) · 2.27 KB
Raw

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) Destination has many reviews and comments
  • Include at least one belongs_to relationship (x belongs_to y e.g. Post belongs_to User) A review belongs to a user and to a destination
  • Include at least one has_many through relationship (x has_many y through z e.g. Recipe has_many Items through Ingredients) users have many destinations through reviews
  • The "through" part of the has_many through includes at least one user submittable attribute (attribute_name e.g. ingredients.quantity) reviews include content and a user-assigned rating
  • Include reasonable validations for simple model objects (list of model objects with validations e.g. User, Recipe, Ingredient, Item) most fields have a valid presence validation. Reviews and comments have a minimum length to ensure quality content
  • 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) Reviews are sorted by rating in the index view
  • Include a nested form writing to an associated model using a custom attribute writer (form URL, model name e.g. /recipe/new, Item) reviews are nested with destinations form
  • Include signup (how e.g. Devise) Used Devise gem
  • Include login (how e.g. Devise) Used Devise gem
  • Include logout (how e.g. Devise) Used Devise gem
  • Include third party signup/login (how e.g. Devise/OmniAuth) Facebook omniauth
  • Include nested resource show or index (URL e.g. users/2/recipes) Reviews and comments are both nested resources of a destination
  • Include nested resource "new" form (URL e.g. recipes/1/ingredients) destination/:id/reviews/new
  • Include form display of validation errors (form URL e.g. /recipes/new) Errors are displayed in a field_with_errors class

Confirm:

  • The application is pretty DRY used before_filter in destination controller, Destination/Review show is shared, several partials
  • Limited logic in controllers
  • Views use helper methods if appropriate
  • Views use partials if appropriate Most forms use partials, error messages are in a partial