[MUSIC]

We can add new wiki pages show pages we've added and then update them.

The only thing missing now is the ability to delete pages.

Let's add that now.

Our wiki.rb file has a page_content method that loads the contents of a text file and

a save_content method that saves a file.

I've added another method called delete_content which deletes a file from

the pages directory.

It simply calls the File.delete method which takes the name of a file to delete.

If you launch a work space from this video's page,

you'll get a wiki.rb file with this method already set up for you.

This time I'll leave testing the method up to.

If you want to experiment with delete content, you can copy it to a separate

file and add a call to it with the name of a file in your pages directory to delete.

You may need to refresh the sidebar before you can see the changes.

Now we just need a way for users to call this method with a particular page title.

Let's set up a button on each wiki page that lets users send a request

to delete that page.

There's one more commonly used request type that Sinatra recognizes and

that's delete request.

But as with put requests,

there's no way to send a delete requests from plain HTML links or forms.

As with put the best way is to create an HTML form and

use a hidden underscore method parameter with a value of delete.

We won't add any text fields to this form,

it's just going to consist of a single delete button.

In the show.erb template, let's add a form element.

We're going to place it within the div element so

that it's easier to style it later.

As before, the only requests type supported by HTML are get and post, so

we'll set the form's method attribute to post.

Then within the form, will add an input element with the type of hidden.

It'll have a name of _method And a value of delete.

That will cause Sinatra to delete the form submission as delete request.

As with all the other requests types, delete request need a path to act on.

We'll set that by adding an action attribute to the form tag.

We'll give it the path of the wiki page we're trying to delete.

That is a slash followed by the page title which will embed using an erb tag.

As before, we can reuse the title instance variable which is already used elsewhere

in the template.

Lastly, we'll need the button that users will click to submit the requests.

Will add an input element with a type of submit.

The value attribute determines what the button will be labeled.

So we'll give it a value of delete this page.

Let's start up our server and run a preview.

And now let's view a wiki page.

We'll see a new Delete This Page button at the bottom.

If we click that button,

we'll see Sinatra doesn't know this ditty again because there's no matching route.

At the bottom of the page,

we'll see a recommendation to create a route using a method named delete.

That means our form submission is being treated as a delete request.

Now we just need to edit our wiki.rb file and add a delete route.

Again, order doesn't matter.

There's no way a delete request will accidentally be matched by

our route's forget, post or put requests.

Just as a method to set up a route for get requests is called GET and the method for

post routes is called POST the method for delete routes is called Delete.

So we'll add a call to that method now.

And you probably know what comes next by now, the path to match.

We set up our form to submit to a path of a slash followed by the current

page title.

So that's what will match here a slash followed by a URL parameter for the title.

And of course we need a block to invoke when the routers match.

In that block, what we'll have to do is call our delete_content method

with the page title and it will delete the appropriate text file for us.

So, we'll call delete_content and give it the title from the URL parameter.

We'll also need to redirect the browser to another page, so

we'll call the redirect method.

We'll just redirect them to the root path.

There's no need to call URI dot escape on the redirect path this time

since there's no chance of it containing an invalid character.

Save that.

Let's restart our server.

And go back to the home page.

We'll create a new page to test our delete functionality out on.

We'll use the title of John Doe and text of just some guy.

Submit it.

And if we go back to our workspace and refresh the file sidebar,

We'll see John Doe.text here in the page's directory.

If we go back to the new page and

click delete, we'll be redirected back to the root path.

And if we refresh our workspace sidebar again, we'll see if

the John Doe.text file has been deleted.