appacademy/bluebird

07-31-2017 Cohort's Lecture FSP

Blue Bird

July 31, 2017 App Academy Cohort

W3D3

• Added bare bones migration files for Users, Chirps, and Likes
• Added basic model validations, associations and custom validations for the above tables

W4D1

• Added routes and controllers for Users, Chirps, and Likes

W4D2

• Added views for Users and Chirps (delaying likes until auth)

bluebird's Issues

Chirps Presentational Components

Make the chirp information in the Redux store display to the page when needed.

Task Presentational Components core feature

Chirps Smooth, bug-free navigation

User Authentication Redux Loop

Allow the front end to request and store session information in the Redux store.

PA Review: Chirps

• Backend:
  • DB
  • model
  • controller
  • views
• Redux Loop:
  • ajax
  • actions
  • reducer
• Presentational Components
• Styling
• Smooth, bug-free navigation
• Adequate and appropriate seeds

User Search Presentational Components

Allow the search results to be displayed on the webpage when needed.

PA Reveiw: Comments

• Backend:
  • DB
  • model
  • controller
  • views
• Redux Loop:
  • ajax
  • actions
  • reducer
• Presentational Components
• Styling
• Smooth, bug-free navigation
• Adequate and appropriate seeds

PA Review: User Authentication

User Auth

can create a user, sign in, sign out, sign up

Chirps Redux Loop

Allow the front end to request and store chirp information in the Redux store.

User Authentication Styling

Style the session pages.

Host site on Heroku

Sign up and make the first push!

User Search Styling

Style the dropdown of user search results.

PA Review: User Search

• Backend:
  • DB
  • model
  • controller
  • views
• Redux Loop:
  • ajax
  • actions
  • reducer
• Presentational Components
• Styling
• Smooth, bug-free navigation
• Adequate and appropriate seeds

Task Redux Loop core feature

User Authentication Smooth, bug-free navigation

Search Users Adequate and appropriate seeds

Seeds.rb: user records need password

Bug in seeds.rb

can't seed the file because of failed validation in user model

user1 = User.create(username: Faker::Name.name, email: Faker::Internet.email)
should be:
user1 = User.create(username: Faker::Name.name, email: Faker::Internet.email, password: 'password')

Task Back End core feature

PA Review: User Auth

• User can log in
• A bunch of other things including styling and everything

Production README.md

Complete the production README for anyone who looks at the repo.

Likes Smooth, bug-free navigation

Likes Backend

DB, model, controller, views.

Do things

PA Review: User Authentication

• Renders errors
  -[ ] can login the user

Likes Adequate and appropriate seeds

User Authentication Adequate and appropriate seeds

new Issue

Wiki Home Page

• Is the first page you see upon entering the wiki
• Contains a welcome message
• Contains a link/placeholder for a link to the live page
• All links in the right sidebar should contain each wiki page and link to the correct page
• Correctly formatted
  • each wiki page is listed in bullet points
  • all links route the correct page

Comments

---

MVP List

• Should have 7 MVPs.
  • 3 of those are User Auth, Heroku, and Production README.
  • The other 4 are from the Approved Apps List or your PM will have clarified them with you
• Contains a description sentence of the app
• Includes two to three detailed bullets on functionality and presentation of feature
• At least one CRUD feature, which states what CRUD operations are planned (creation, reading, updating, deletion)
• Estimates how long it will take the code each MVP
• Correctly formatted
  • MVPs are listed in an ordered list
  • Each MVP is broken down into bullet points

Comments

---

Database Schema

• Contains correct datatypes
• Contains appropriate constraints/details
  • primary key
  • not null
  • unique
  • indexed
  • foreign key
• Contains bullet points after the table that state which foreign keys will reference to which table, or references to the associations which will be made
• foreign key and table name are lowercased, snake_cased and back_ticked
• Correctly formatted
  • schema is written in a table format
  • the table's name are lowercased, snake_cased and back_ticked
  • the table header column names are bolded
  • columns names are lowercased and snaked_cased and back_ticked

Comments

---

Sample State

• State shape is flat!
• State's keys are camelCased
• All keys within the values in the state are accessible in the schema
• Correctly formatted
  • Sample state is rendered with triple backticks, and the language ```javascript...```). This will display the state as a code block instead of a giant line of text
  • Top level slices
    • entities
    • session
    • errors (here or in ui)
    • ui (if needed)
  • Should NOT have nested slices, aka comments inside of posts
  • Some info from other tables is ok, for instance:
  • the author username and imageurl for a post. basically any info that the user can't change
  • like count and a boolean on whether the user likes the post instead of a likes slice

Comments

---

Backend Routes

• Contains the following sections: HTML, API Endpoints(Backend)
• Each route has a description
• API Endpoint routes contains wildcard variables written in snake_case
• Routes does not contain superfluous routes
• Have API routes that will allow the front end to get all info it needs and does not have unneeded routes:
  • probably doesn't need a GET likes api endpoint because that info comes through the post show

Comments

---

Frontend Routes

• Frontend routes contains wildcard variables written in camelCase
• Correctly formatted
  • Routes are displayed with inline coding text (backticks)

Comments

Likes Redux Loop

Incorporate create and request likes information from the front-end and put it in the redux store.

Likes Presentational Components

Incorporate Likes information into the Chirp presentational components.

User Authentication Backend

DB: users
Model: user
Controller: users, session
Views: users, session

Chirps Back End

DB, model, controller, views

PA Review: Production README.md

Content:

• Has a # Title
• Links to the Wiki design documents
• Describes technologies used
• Describes core functionality
• Lists future directions
• Fills out Description and Website at the top of the repo.

Format:

• Uses markdown formatting
• Includes code snippets (with triple backticks, and the language ```javascript...```)
• Includes screenshots / gifs

Optional:

• Describes technical challenges
• Add topics to the top of the repo

Dashboard and Profile View Smooth, bug-free navigation

Likes Styling

Style the part of the chirp presentational component that displays the like count.

PA Review: Likes

• Backend:
  • DB
  • model
  • controller
  • views
• Redux Loop:
  • ajax
  • actions
  • reducer
• Presentational Components
• Styling
• Smooth, bug-free navigation
• Adequate and appropriate seeds

Chirps Styling

Add style to Chirp presentational components.

Dashboard and Profile View Presentational Components

Select and present chirps from the store that are from one particular user.

PA Review: User Authentication

• Backend: DB, model, controller, views
• Redux Loop: ajax, actions, reducer
• Presentational Components
• Styling
  • When errors are displayed, the form adjusts properly (input boxes move up, sign in/sign up button moves down, and errors are displayed in between)
• Smooth, bug free navigation
  • Login errors clears when switching from login form to sign up form (and vice-versa)
  • Going to a random route /#/oweiniouewbrviuwebv should redirect to either /, /login, or /signup
  • Errors should display for both /signup and/login.
  • Errors should clear when moving between /signup and /login.
• Adequate and appropriate seeds
  • Demo Login Works

PA Review: Profile View

• Backend:
  • DB
  • model
  • controller
  • views
• Redux Loop:
  • ajax
  • actions
  • reducer
• Presentational Components
• Styling
• Smooth, bug-free navigation
• Adequate and appropriate seeds

PA Review: User Auth

• Users can sign up, sign in, log out
• Users can use a demo login to try the site
• Users can't use certain features without logging in (creating chirps & likes)
• styled to perfection
• no bugs except "features"

PA Review: Hosting on Heroku

Initial Deployment:

• Initial push to heroku

Final Deployment:

• Remove console statements: debuggers, console.logs, errors, minification warnings, mixed content warnings
• Use dev tools in dev environment

Bonus:

• Custom domain name

Search Users Smooth, bug-free navigation

User Search Redux Loop

Allow Redux store to keep information about the user search results based on a string.

Chirps Adequate and appropriate seeds

User Authentication Presentational Components

Make the session information in the Redux store display to the page when needed.
Make needed Protected and Auth Router routes.

Dashboard and Profile View Adequate and appropriate seeds