Skip to content

Conversation

@Shonda860
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 A model is a class that is called in database. Tasks is a class
Describe in your own words what the Controller is doing in Rails Is the go-between for views and models. Tasks controller have many methods that help render the views
Describe in your own words what the View is doing in Rails views is what the user will see based on the path they are routed to. The method determines how the data that is used in corresponding view/html-erb file.
Describe an edge-case controller test you wrote if a user updates page but incorrect/invalid id used
What is the purpose of using strong params? (i.e. the params method in the controller) uses task id fewer errors
How are Rails migrations related to Rails models? using migrations you can keep track of every time you make a change to the data structure.
Describe one area of Rails that are still unclear on Testing ??.also why does all the instructor test show as (...) instead of show all the test pass or fail again?? I believe Devin explained at one point but can't remember.

@jmaddox19
Copy link

Task List

Major Learning Goals/Code Review

Criteria yes/no, and optionally any details/lines of code to reference
At least 6 commits with meaningful commit messages ✔️
Routes follow RESTful conventions ✔️
Uses named routes (like _path) ✔️
Creates Models and migrations ✔️
Creates styled views no, but not required
Handles errors like nonexistant tasks ✔️
Uses form_with to render forms in Rails ✔️

Functional Requirements/Manual Testing

Functional Requirement yes/no
Successfully handles index & show ✔️
index & show tests pass ✔️
Successfully handles: New, Create ✔️
New, Create tests pass ✔️
Successfully handles: Edit, Update ✔️
Successfully handles: Destroy, Task Complete Destroy is working because it's spelled incorrectly in the TasksController. This is a good reminder to manually test your changes :)

Overall Feedback

Overall Feedback Criteria yes/no
Green (Meets/Exceeds Standards) 5+ in Code Review && 5+ in Functional Requirements ✔️
Yellow (Approaches Standards) 3+ in Code Review && 4+ in Functional Requirements, or the instructor judges that this project needs special attention
Red (Not at Standard) 0-2 in Code Review or 0-3 in Functional Reqs, or assignment is breaking/doesn’t run with less than 5 minutes of debugging, or the instructor judges that this project needs special attention

Code Style Bonus Awards

Was the code particularly impressive in code style for any of these reasons (or more...?)

Quality Yes?
Perfect Indentation

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