This is a sample API app for a butcher shop. It's broken and incomplete. Your job is to fix it and finish it.

What we'd like you to do is the following:

This app has a bunch of tests. Some of them are failing, and some of them are broken. You must get all tests to pass

There is a user model, but it's currently pointless. Let's make it have meaning in life by adding a new model that belongs to users called Favorite. Users can have many favorites and a favorite has a cut of meat. In addition to creating the model, you must create a set of resources for favorites that allows you to view all of a user's favorites, and create, update, and destroy. These resources would have the following routes:

• GET /users/:id/favorites
• POST /users/:id/favorites
• GET /favorites/:id
• PUT /favorites/:id
• DELETE /favorites/:id

No other routes should be added to the app, and all these requests can be handled by one controller. Make sure you add tests for your controller and model where appropriate.

Finally, the response for GET /users/:id/favorites should include the cut of meat, not just the cut_id. For example:

{
  favorites: [
    {
      ... favorite attributes
      cut: {
        name: "whatever"
        ... cut attrs
      }
    }
  ]
}

HINT: You can pull this nesting off with one line in a serializer

Finally, we'd like to add some database seeds to the seeds.rb file. Please make the seeds create the following:

• Animals:
  • Cow
    • Primal Cuts:
      • Chuck
      • Short Loin
      • Rib
        • Cuts:
          • Prime Rib
          • Ribeye
    • Cuts:
      • Porterhouse
      • T-bone
      • Strip
  • Pig
    • Primal Cuts:
      • Jowl
      • Ham
      • Loin
        • Cuts:
          • Loin Chop
          • Blade Roast
    • Cuts:
      • Babyback Rips
      • Spareribs
      • Hock

The items in bold represent the models, and the items under represent the entries to create.

Please note that this app uses the rails-api gem, and is not a traditional rails app. Nothing that is broken in this app is a trick, you should be able to fix everything with a basic knowledge of rails and by reading the errors.

Simply fork this repo on github, then submit a pull request when you've completed the tasks.