Conversation
Task ListMajor Learning Goals/Code Review
Functional Requirements/Manual Testing
Overall Feedback
Code Style Bonus AwardsWas the code particularly impressive in code style for any of these reasons (or more...?)
|
beccaelenzil
left a comment
There was a problem hiding this comment.
Great work on this project. It's stylin` and the user experience is superb. Furthermore, nice work fleshing out the tests for create, update, and destroy. It is clear that the learning goals for this were met. Keep up the hard work!
|
|
||
| resources :tasks | ||
|
|
||
| patch '/tasks/:id/complete', to: 'tasks#completed?', as: 'complete_task' # Mark completion of task. |
There was a problem hiding this comment.
Consider how making two separate methods, for instance mark_complete and mark_incomplete would make this action idempotent.
| end | ||
|
|
||
| # Complete these tests for Wave 4 | ||
| describe "destroy" do |
There was a problem hiding this comment.
Great work fleshing out the test for changes to the db. For a thorough destroy test you should also test what happens for an invalid task id.
| // They will automatically be included in application.css. | ||
| // You can use Sass (SCSS) here: https://sass-lang.com/ | ||
|
|
||
| .task-container { |
| </section> | ||
|
|
||
| <nav class="options <%= 'options--completed' if task.completed_at != nil %>"> | ||
| <% if task.completed_at == nil %> |
There was a problem hiding this comment.
Consider using a ternary for this conditional view logic.
Task List
Congratulations! You're submitting your assignment!
Comprehension Questions