Section 1

Preview this deck

if statement

Front

Star 0%
Star 0%
Star 0%
Star 0%
Star 0%

0.0

0 reviews

5
0
4
0
3
0
2
0
1
0

Active users

0

All-time users

0

Favorites

0

Last updated

6 years ago

Date created

Mar 1, 2020

Cards (23)

Section 1

(23 cards)

if statement

Front

something that determines wether or not a requirement is met and will or will not run that code

Back

delete

Front

method requests that the server delete the resource identified by the Request URI. This means... that it deletes the record. It's nice and explicit.

Back

session

Front

is a way for a web application to set a cookie that persists an identifier across multiple HTTP requests, and then relate these requests to each other: If you've signed in before the web application will be able to know that you're still the same user you've identified as a couple requests earlier. If you've done something else before, and something has been stored to your session, then the web application will be able to use it later.

Back

each method

Front

Executes an action using as parameter each element of the array. Returns the unmodified array.

Back

find method

Front

Take an expression and returns the first element for which the expression returns true:

Back

params

Front

is a hash of key/value pairs that comes from the browser. It is additional data that the browser includes with their request.

Back

has_secure_password

Front

Adds methods to set and authenticate against a BCrypt password. This mechanism requires you to have a password_digest attribute.

Back

View

Front

Responsible for showing end user content

Back

map method

Front

Performs an action on each array element. The original array is not modified. Returns the modified array.

Back

redirect

Front

is used to tell the browser to issue a new request

Back

RESTful

Front

routes have a clear mapping between the URL resource and the corresponding controller actions.

Back

REST

Front

is an architectural design pattern, not a framework or code in itself. Many other web frameworks utilize RESTful design principles in some form or another. By using RESTful principles, Rails apps are able to have a clear and standardized naming structure for routes and actions.

Back

Model View Controller

Front

Also known as MVC, is a software architecture, the structure of the system

Back

Model

Front

interacts with database. Gets and sends data. Runs database logic.

Back

find_by

Front

find a specific line of code and returns it

Back

patch

Front

methods both represent the HTTP verbs that are used to update existing resources. So if you sent a PUT request to /posts/1 with a new post name, the post with an id of 1 would be updated.

Back

Controller

Front

Gets requests from view, sends to model. Gets appropriate response from model, sends to view.

Back

erb

Front

also known as render only works in case the controller is being set up properly with the variables that needs to be rendered.

Back

get

Front

method retrieves whatever information is identified by the Request URI. This means if you go to /posts, you will get all of the posts that the application wants your application to have.

Back

select method

Front

Runs an expression for each array element and, if it is true, that element gets added to the output which is returned. This is called filter in other languages.

Back

post

Front

method is used to send data enclosed in the request to the server. The server is expected to use this data to create some new resource.

Back

class

Front

When a new ___ is created, an object of type ___ is initialized and assigned to a global constant

Back

module

Front

In Ruby, ___ are somewhat similar to classes: they are things that hold methods, just like classes do. However, ___ can not be instantiated

Back