Queues - Elizabeth Deutsch - Task List

[edeutschie]

Task List

Congratulations! You're submitting your assignment!

Comprehension Questions

Question	Answer
Describe in your own words what the Model is doing in Rails	The Model takes the direction (methods called) from the Controller and accesses the database of information via ActiveRecord and returns the data results to the Controller.
Describe in your own words what the Controller is doing in Rails	The Controller is where the ruby (in the case of Rails) logic and variables are stored. When a request comes in from the user, the controller calls the appropriate methods needed to give the user what they want and relays them to the Model where the data to be acted on is stored. When the Controller gets the info/data back from the Model, the Controller relays it to the View and asks the View to present it to the user.
Describe in your own words what the View is doing in Rails	The View holds the placeholder html content to send to the browser after a user request. It puts whatever the user requests (relayed to the View by the database via the Model and Controller) into html form which is then displayed in the browser in a consumable way by the user.
What is the purpose of using strong params? (i.e. the params method in the controller)	Strong params protect the program from being damaged by users and other outside influences. It limits the input it will accept so that malicious input can't make it through and damage the program and database.
How are Rails migrations related to Rails models?	Rails migrations are the specifications to the Rails model of how the database should be arranged - they create the structure of the database. Additional migrations allow changes to be made to that structure (columns added, column names changed, etc.).
Describe one area of Rails that are still unclear on	Trying to describe what is happening is really challenging for me. The above answers felt pretty shaky. Also, tracing the patterns of the paths/putting into words what is going on in the routes.rb and using the terminology is really difficult for me.

P.S. I noticed after my last commit that I left some lines commented out in certain files (the controller, css, etc.). I wasn't sure how to back out of my pull request at that point, so they are still in there.

P.P.S. I thought I did more commits!

[droberts-sea]

Task List

What We're Looking For

Feature	Feedback
Baseline
Appropriate Git Usage with no extraneous files checked in	Your commit messages are pretty good, but make sure you're remembering to commit regularly! For an example of a good cadence in the context of Rails, see the commit history from last week's live code
Answered comprehension questions	yes
Successfully handles: Index, Show	yes
Successfully handles: New, Create	yes
Successfully handles: Edit, Update	yes
Successfully handles: Destroy, Task Complete	yes
Routes follow RESTful conventions	yes
Uses named routes (like _path)	yes
Overall

Looks good!