Task List

Let's build a Task List in Rails! We will solve the problem of tracking tasks in a web application. This project will enable us to keep track of and persist, add, edit and remove tasks.

Frequently Asked Questions

Due October Seventh!?

THIS IS COHORT 12's TASK LIST. Are you in Cohort 13? If so you probably meant to use Cohort 13's Task List.

Wait, I'm in Cohort 13 how did I get here then?

That's our bad, we forgot to update the calendar link from last time to point at this Cohort's fork of task-list. Sorry about that!

Oh no, I forked this already!

Don't panic! You will need to delete your old C12 fork and create a new C13 fork. If you haven't made any commits already then you're good to go after doing this.

Umm... what if I already made some commits?

Things are a little more involved. Don't worry. Just let an instructor know and we will make sure to grade your fork from the C12 repository.

At a Glance

• Individual, stage 1 project
• Due before class on Monday Oct. 7th

Learning Goals

Practice all aspects of Rails development.

• Create a new Rails application
• Explore each aspect of the Rails Request Cycle: Model, View, Controller
• Implement RESTful routes using Rails standards
• Complete all CRUD actions in a Rails application

Baseline

In this baseline, you'll create a new Rails application and get started with two of the major components: route, controller and view.

• Fork and clone this repository to your computer
• Create a new Rails application using rails new .
  • create a Tasks controller
  • create a route to view the task index page
  • create a controller action for the task index page which contains an array of hard-coded tasks
  • create an ERB view to display the tasks from the controller action

Controller Tests

Tests have been created for waves 1 & 2. You can find the tests in test/controllers/tasks_controller_test.rb, and you can execute the tests with $ rails test. You may need to update the test file if your schema differs from the one in the spec. For waves 3 & 4, you will need to fill in your own tests.

Wave 1

This wave is where we introduce ActiveRecord to create a model. We use the model to persist our data. Make sure you are building the application so that it meets the requirements of the pre-written tests.

1. create a migration which will create a new Task model
   • create the database schema and tables by running the rails db:migrate command
   • the Task model should include at least a name, a description and a completion date
   • create at least 2 Task model instances using the rails console
2. update the controller's index action you created to retrieve and show all Task objects from the database
   • you may need to update the view as well to use the model fields rather than the hard-coded data

Wave 2

In this wave, we will expand the actions we support and introduce forms for user interactivity and persistence. Again, make sure you are building the application so that it meets the requirements of the pre-written tests.

1. add support to show each task
   • update the task list to link to a show action for each individual task
   • create a route
   • create a controller action
   • create an ERB view
2. Create a new task:
   • update the task list to have a link to add a new task
     • this will give the user a new page with a form with the appropriate task fields
     • the site should take the user back to the task list after the new task is added
3. Verify the success of your controller actions by uncommenting the wave 2 tests and executing them with $ rails test.

Wave 3

In this wave we will extend the interactivity with users, allowing them to edit existing tasks.

1. Complete tests by uncommenting and filling in the contents of the Wave 3 tests for the edit and update actions.

2. Edit a task

   • update each task's show page to include an edit link
     • this will give the user a new page with a form that is pre-populated with the data about that task
     • the site should take the user back to the task's show page after the task is updated

3. Optional

• DRY up your code by reusing the view code from the new functionality
  • Hint: Rendering partials in Rails

Wave 4

In this wave, we will add the ability to delete tasks. We will also add the ability for a user to mark a task complete. Note: Marking a task complete will require going above and beyond the examples provided in lecture. You will also need to write controller tests for the delete and mark complete actions.

1. Delete a task
   On the task list, add a button or link for each task that will, once clicked:
   1. Ask the user to confirm that they definitely want to delete the task.
   2. Delete the task from the database and redirect the user back to the list of remaining tasks
2. Mark a task complete
   • Add a button to the list of tasks on the home page that, when clicked, will mark a task complete
   • Update the database with the task's completed date

Optional Design

The focus of this project is to familiarize yourself with rails. Design of this application is optional and secondary to learning goals this project. If you do find you have time to style the design of your application, you can use or own design or the wireframes below.