Skip to content

Latest commit

 

History

History
45 lines (36 loc) · 2.42 KB

spec.md

File metadata and controls

45 lines (36 loc) · 2.42 KB

Specifications for the Rails with jQuery Assessment

Specs:

  • Use jQuery for implementing new requirements
  • Include a show page rendered using jQuery and an Active Model Serialization JSON backend.
  • [] Include an index page rendered using jQuery and an Active Model Serialization JSON backend.
  • Include at least one has_many relationship in information rendered via JSON
  • Include at least one link that loads or updates a resource without reloading the page
  • Translate JSON responses into js model objects
  • At least one of the js model objects must have at least one method added by your code to the prototype

Confirm

  • You have a large number of small Git commits
  • Your commit messages are meaningful
  • You made the changes in a commit that relate to the commit message
  • You don't include changes in a commit that aren't related to the commit message

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)
  • Include at least one belongs_to relationship (x belongs_to y e.g. Post belongs_to User)
  • Include at least one has_many through relationship (x has_many y through z e.g. Recipe has_many Items through Ingredients)
  • The "through" part of the has_many through includes at least one user submittable attribute (attribute_name e.g. ingredients.quantity)
  • Include reasonable validations for simple model objects (list of model objects with validations e.g. User, Recipe, Ingredient, Item)
  • 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)
  • Include a nested form writing to an associated model using a custom attribute writer (form URL, model name e.g. /recipe/new, Item)
  • Include signup (how e.g. Devise)
  • Include login (how e.g. Devise)
  • Include logout (how e.g. Devise)
  • Include third party signup/login (how e.g. Devise/OmniAuth)
  • Include nested resource show or index (URL e.g. users/2/recipes)
  • Include nested resource "new" form (URL e.g. recipes/1/ingredients)
  • Include form display of validation errors (form URL e.g. /recipes/new)

Confirm:

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