sf-wdi-labs / public-library-app

[rails, associations, many-to-many, auth]

Public Library App

Overview

Your goal is to build a membership-tracking application in Ruby on Rails - for public libraries. Your app will allow users to sign up and track their memberships in various libraries.

Goals

By the end of this lab you will have:

• Basic-Auth: sign up, log in, log out
• Basic views for your users
• A Many-to-Many database relationship: Users, Libraries, Library Users
• "Skinny" controllers

Getting Started

Do not fork and clone this repo, as you will be creating a new Rails project. You should, however, track your project in git and GitHub. Make frequent commits with descriptive commit messages!

Part 1: Users & Auth

Solution branch: 1_users_and_auth

Part 2: Library Users

Solution branch: 2_library_users

public-library-app's Issues

inherit from ApplicationRecord

update models to inherit from new ApplicationRecord class instead of ActiveRecord::Base

modify approach to CRUDing memberships

Should be cruding the join table. Leads to cleaner / more restful routes.

e.g. (better)

POST /library_users  ?user_id=10&library_id=20  # create a membership
DELETE /library_users/:id                 # destroy a membership

Current (less clear):

POST /libraries/:id/users            #create a new user for a specific(?) library

`logged_in?` helper should not redirect

logged_in? is overload. It should return a boolean and should not trigger a redirect.

`logout` helper created and not used

In part 1, we create a logout helper but don't use it.

Thanks @alyshae!

Edit Instructions

in Part I, while making the new user form, the instructions say that, once you make your template, you should be able to see the form. We found this to be false. You, in fact, have to build your POST route and add a 'create' method to your controller before the page will actually show.