Skip to main content

Seven RESTful Routes You Should Know!


I have been followed the course to develop several app projects. They all follow the RESTful route pattern. Today, I learned many key points about RESTful and would like to share my study note here.

What Is REST?

REST stands for representational state transfer. I don't know what does this mean, but it is not important right now. You just need to know that REST is just a pattern for defining our routes.

What's The Point Of REST?

The important things for us is to define what REST is.

REST is a way of mapping HTTP routes and CRUD functionality together. By the way CRUD stands for Create, Read, Update, and Destroy.

The point of REST is that we don't do whatever we want. Instead, we follow a pattern. It is also more reliable so that if we are interacting with a restful API, it follows a particular pattern.

Seven RESTful Routes

The course lists the seven route table. It just acts as a pattern that we can fill in the blanks when we develop our own App.

screenshot from course
1. Index Route

The URL is "/dogs", and you can change the "/XX" depends on your App. The purpose is to list all the relevant data, in this case, all dogs.

2. New & Create Routes

New and Create routes are linked to each other. Both of them are for creating new data.

The HTTP verb of Create is "Post". The post is where we go to post form data to create a new data and then redirect to somewhere.

3. Show Route

The point of Show route is to show detail information about one particular data.

4. Edit & Update Routes

Edit and Update routes are linked to each other, too. They correspond to one another.

Edit is going to show us the form. Update is where the form submits.

Moreover, Update's HTTP verb is "Put" request. The process inside Update is that we need to find the old data first and then update it with new data. The purpose of  "Put" request is to update something rather than posting new things.

5. Destroy

Destroy is a single route. It's going to delete request to the "/dogs/:id". The point is that Destroy leads to a particular thing and then redirect somewhere.


Comments

Popular posts from this blog

Intermediate Express.js: How To Add Styles & Partials in EJS File?

So far, we only have simple HTML tags and ejs tags in each ejs file. Every template page has no style at all. And the basic HTML header and footer are also missing. Today, I learned how to add styles and partials in ejs file. Link Style Step One: Touch a Separate CSS file I create a new directory "Style" under the "EJSDemo" directory, then I add a new CSS file "app.css" inside "Style" folder. Step Two: Add app.use(express.static()) in the app.js I add app.use(express.static("style")) in the "app.js". This will tell Express.js to serve the content of "Style" directory. Step Three: Write styles in CSS file I simple give body an orange background color and set text color to be grey. Step Four: Link to CSS file in the EJS file I just add <link> tag to link the "app.css" file on the top of the h1 tag in each ejs template. As the result, when I run the app and...

Intermediate Express.Js: Write Conditions and Loops In The EJS (study note)

We continue to use the app.js which we have build to be the study example. In the last post, we only add a simple EJS tag <%= thingVar %> inside h1 tag. This will match the "thing" to any "thing" request from the user. If Statement Today, the course shows us to write a simple if statement in the EJS file. I learn to apply it to my own app. In the if statement, if users send"/wantto/workout" request, the page will show a new content "Good Idea!". We wrote the if statement in the "diet.ejs" file, and we add "<% %>" tags around the code. We have to wrap every line of JavaScript anytime JavaScript starts and ends. Moreover, you may see there are two types of ejs tags here: <%= %> The one with equal sign. According to the course, when we add equal sign, the value that is returned inside of the tag will be rendered to the HTML page. it will be added to the HTML. For example, if we write ...

Authentication Project: Secret Page App Part One (Set up & Create User Model)

So far we only write the RESTful routes to send request and redirect to the related page, but we haven't do anything about authentication. If we can sign up, login, and log out, it will make our app more meaningful. Therefore, the course shows us how to create a secret page app, which will allow us to sign up, login to a secret page, and logout. Since it requires so many pieces, I will divided this project into three parts: set up & create user model, sign up, and login/logout. In this post, I am going to show all the set up process. Set Up Step One: Install packages The first thing we are going to do to create a folder "Auth", and inside of "Auth", we need to create another folder "AuthDemo". Then we cd (change directory) to "AuthDemo". Now we can set up the actual application structure by installing a few packages: passport, passport-local, passport-local-mongoose, mongoose, express, ejs, body-parser, and express-session....