- Define CRUD.
- There are seven verb + path combinations that are necessary in a basic Sinatra app in order to provide full CRUD functionality. List each of the seven combinations, and explain what each is for.
- Why do we use
set method_override: true? - Explain the difference between
valueandnamein this line:<input type='text' name='task[title]' value="<%= @task.title %>"/>. - What are
params? Where do they come from?
-
-
Save PenneyGadget/a4d2bc78fe8f1e0bead5 to your computer and use it in GitHub Desktop.
CRUD in Sinatra -- Check for Understanding
Author
#1, #2, and #3 look good!
#4: "name" refers to what will become the key in the params hash. "value" is what will actually be displayed to the user through the browser.
#5: params can also come from data that the user enters in a form.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1.) GET + '/tasks' - see all our tasks
2.) GET + '/tasks/:id - see an individual task
3.) GET + /tasks/new' - see a form to create a new task
4.) POST + '/tasks' - click submit and create a new task
5.) GET + '/tasks/:id/edit' - see a form to edit an existing task
6.) PUT + 'tasks/:id' - click update to update the edited task
7.) DELETE + 'tasks/:id' - delete a task