Skip to content

Latest commit

 

History

History
126 lines (93 loc) · 3.83 KB

NOTES.md

File metadata and controls

126 lines (93 loc) · 3.83 KB

Step 1: Integrate Basic Theme to Asset Pipeline

  • [X]/ - Go to home page and see a stubbed out, non-dynamic page with theme

Step 2: Allow people to CRUD lists

  • ListsController #index -see all the lists -doubling as #new in that it present the person with a form to create a new list / - Index all the lists

    -create a lists

-show a list

Want people to be able to create lists Then be able to add items to those lists They should be able to navigate many lists And see each lists items

Need a Model and Controller(create resource)

MODELS lists has many items

items belongs to a list

-Does it impact my DB? -Does it impact my URLs? '/lists/1'

Step 3: Add Items to a List

  • come back to Refactor Views into Partials and Helpers once TodoMVC 2 is completed

  • TodoMVC 2 is: Lists have Items, i'll be able to add Item piece(MVC) 102218

  • [x]Make Items to List List has many Items 2 Grocery List

    Every Item belongs to a List id description list_id(foreign key) 1 bananas 2 2 apples 2

  • [x]Make items a List real

  • [x]Need and Item table: associated with a List

  • [x]#create for and item in a List: what is the HTTP URL method

  • the form is present in the list show page

  • what URL does this imply?

POST /items #=> doesn't describe which list we are adding an item to An Item doesn't exist in app outside of context of the List it belongs to

  • Nested Resources : /lists/:id/items (Items are nested within this List, in terms of URL )

Step 4: Adding Validations

  • [x]validate that Lists have a name
  • [x]validate that Items have a description

Step 5: Add state(complete, incomplete) to Items in a List

-get it working without JS or AJAX to build out more of the logic without complexity of JS

-what URLs are needed and how might DB change -idea of item being complete/incomplete requires data -new forms for updating item status which means new URL /lists/1/items PUT/PATCH to /lists/1/items/1 -Updating Item 1 in List 1 PUT/PATCH to /lists/:list_id/items/:id

-need to steal checkbox HTML from TodoMVC dot com -add this to view

-also need JS function to submit form with checkbox click $(function(){ $('input.toggle').on('change', function(){ $(this).parents('form').trigger('submit') }) })

-When you uncheck a box of an Item, the browser shouldn't submit any data -When you check a box of an Item, then the browser does submit and change data

REFACTOR:

  1. start using partials in lists/show (fixed the content_tag_for issue in browser. just has to restart server!!!)

Step 6: Delete an Item or List

  • [x]need a new button/link for delete feature
  • [x]needs to his a URL -RESTful convention: DELETE /lists/:list_id/items/:id -how to trigger a delete request -browsers only support GET(link) and POST(form submission)
  • [x]Need controller action to process deletion of Item

Step 7: Add user sign up/logging in AND now incorporate OmniAuth

Step 8: User has lists and can only see their own list

Believe there are 5 total TodoMVC stages to complete 1.Assets and Managing Lists 2.Lists have Items 3.Mark Items Complete 4.Refactoring with Partials & Helpers 5.Deleting Items

100418 -not sure if this will change again with TodoMVC 2-5 code alongs, will see -most up to date code is different from code along presentation -therefore i don't have all the correct code and that's why my form isn't working -code along is actually out of order, when i am at the correct part then i will be able to work out this part of the application(partials and helpers)

110118 -created new branch for authentication -i may merge it later if i really love the auth feature -also want to create a layout with a home button(at some point, not pertinent) -maybe work on helper methods for lists as similar to items

-currently just working on new branch details before continuing with authentication