Skip to content

Latest commit

 

History

History
42 lines (38 loc) · 2.51 KB

CHECKLIST.md

File metadata and controls

42 lines (38 loc) · 2.51 KB
Raw

Specifications for the Rails Assessment

Specs:

  • Using Ruby on Rails for the project Self explanatory, using Rails as project framework.
  • Include at least one has_many relationship User has_many projects, Project has_many comments
  • Include at least one belongs_to relationship (x belongs_to y; e.g. Post belongs_to User) Comment belongs_to Project, Comment 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 FlatironModules through Project User has_many Comments through Projects
  • 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 Comment through Project, Comment has_many Users through Project
  • 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) User has_many Comments through Projects, comments have user submittable :body
  • Include reasonable validations for simple model objects (list of model objects with validations e.g. User, Recipe, Ingredient, Item) User, Project, 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) Project class includes
  • Include signup signup_path to devise/registrations#new
  • Include login login_path to devise/sessions#new
  • Include logout logout_path to devise/sessions#destroy
  • Include third party signup/login (how e.g. Devise/OmniAuth) Used the following gems: 'dotenv-rails', 'omniauth', 'omniauth-github' to help with authentication
  • Include nested resource show or index (URL e.g. users/2/recipes) Nested Comment show/index "project_comment_path" /projects/:project_id/comments/:id
  • Include nested resource "new" form (URL e.g. recipes/1/ingredients/new) Nested Comment new form "new_project_comment_path" /projects/:project_id/comments/new
  • Include form display of validation errors (form URL e.g. /recipes/new) Signup form displays validation errors

Confirm:

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