antleo1995 / jquery-ajax-delete

jQuery AJAX Delete Element

Prerequisites

• http-study
• json-study
• Ajax Get Collection
• Ajax Get Element

Objectives

Make HTTP requests using curl and AJAX to:

• Delete a specific resource.

Use response data in future requests

Preparation

1. Fork and clone this repository.
2. Create and checkout a new branch (training).
3. Install dependencies with npm install.

You can access the same web server that we set up during jquery-ajax-get-collection. Just leave the server running at the same port.

If you need to set up the web server from scatch:

We'll make requests of and receive responses from an HTTP server we'll set up together:

1. Open a new terminal (window or tab).
2. Change into ~/wdi/tmp.
3. Fork and clone library-api-guide and follow installation instructions listed there.
4. Once installed, checkout a jquery-ajax branch within library-api.

We're now ready to make requests.

DELETE /books/:id

Delete a book from the API

Review: GET Single Book

First let's ensure we can get a book with a specific id.

Enter http://localhost:4741/books/1 into the chrome address bar to retreive a single book with id=1

We can also use curl to retrieve one book at a time.

Demo: Delete Single Book using Curl

We'll use curl with the DELETE http verb to signify to our API that we want to delete the book

Why can't we delete a book using the browser address bar?

Code Along: Write Curl Script

Let's write that curl command into a script.

Lab: AJAX Delete Single Book

Again, take a stepped approach:

1. Add a new form with text input for a book id to the form in index.html.
2. Add a Delete button to the form
3. Retrieve the value of the id, if any, in the submit handler.
4. Branch on that value in the submit handler.
5. Add a delete single book success and fail handler to assets/scripts/books/ui.js.
6. Add a delete single book method to assets/scripts/books/api.js.
7. Invoke the delete single book method from the submit handler passing the success and fail callbacks.

License

1. All content is licensed under a CC­BY­NC­SA 4.0 license.
2. All software code is licensed under GNU GPLv3. For commercial use or alternative licensing, please contact [email protected].