Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lynn Trickey's Task List #26

Open
wants to merge 45 commits into
base: master
Choose a base branch
from
Open

Lynn Trickey's Task List #26

wants to merge 45 commits into from

Conversation

ltrickey
Copy link

Task List

Congratulations! You're submitting your assignment!

Comprehension Questions

Question Answer
Describe in your own words what the Model is doing in Rails Model creates the type of object and accesses information in the database. Since a lot of the stuff we've been doing with the model seems like rails magic, I'm less sure about how we'll work with it in the future. Right now it creates a type of object (task or books) that inherits from ApplicationRecords, so it inherits a lot of behavior. I know this is eventually where business logic will be, so I imagine we'll write specific methods depending on the type of information we are accessing in the future.
Describe in your own words what the Controller is doing in Rails Controller is the go between for the Model, View and Browser. The controller gets information from the Browser, through the routes, and then calls specific actions in order to get information from the database through the Model, then takes that info, gets the appropriate view for it, renders it and gets it back to the user in the browser. Sort of the conductor of the rails app.
Describe in your own words what the View is doing in Rails View says how to present the information to the user in the browser. Keeps all the html and erb and styles.
What is the purpose of using strong params? (i.e. the params method in the controller) Strong Params prevents users from putting in bad data that can mess up your database by controlling exactly what information from the form we will access and update our db with.
How are Rails migrations related to Rails models? Rails migrations edit the database that the rails model uses. So I might have a migration to add a column in my db of "date" which will then become an accessor method for that db object. I can call .date and display or update the date saved in the database associated with that specific model object.
Describe one area of Rails that are still unclear on How we'll build out Models - what types of methods we'll write there.

ltrickey added 30 commits March 20, 2017 14:39
@CheezItMan
Copy link

Task List

What We're Looking For

Feature Feedback
Baseline
Appropriate Git Usage with no extraneous files checked in Check a good number of commits with useful messages.
Answered comprehension questions Check, one thing I would emphasize is that migrations change the structure of the database, not the content. Hopefully the next project will make model methods a bit clearer.
Successfully handles: Index, Show VERY nicely styled. You have the show & index actions down.
Successfully handles: New, Create Check
Successfully handles: Edit, Update Check
Successfully handles: Destroy, Task Complete Check, you could also use link_to or button_to instead of a separate form simply to mark a task as complete.
Routes follow RESTful conventions Check
Uses named routes (like _path) Check, good use of the path helpers.
Overall Very well done Lynn, I very much like how you styled the site. It looks good. On the index page, why did you make it so that tasks cannot be deleted unless they are marked complete?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants