#flux cycle

Friendex

Tested and fixed Friendship Buttons

Dynamically display relevant "Add Friend", "Confirm"/"Delete Request", "Friends" button in Profile Header depending on current friendship between currentUser and currentProfile

Confirm / Delete Request - pass in "page" param to make sure the correct friend info is pulled & returned once friendship is updated (whether confirming from requestor's profile page or receiver's friends page)

Display Friend Requests only when a user is visiting their own page

Display "Remove Friend" button in FriendsIndex only when visiting own Friends page

Notes

You cannot make an :index route on a singular resource. Only the following come by default:

new

create

edit

update

show

destroy

Realized this when trying to write a route for Newsfeed - must use :show rather than :index

Make sure to specify your file types!!

Forgetting the .json.jbuilder file ending on view partials will not return anything when those views are rendered

Friendex

Refactored Header vs Content

Current user was not getting passed to children correctly, fixed so that SessionStore tracks currentUser and currentUserProfile

Refactor Profile & ProfileAbout component - separate header from content so can use modularly

Set CSS styling so that ProfileAbout renders cleanly when in just a sidebar as well as when it stretches across the entire page

Built Post CRUD - can create, update, and destroy posts via AJAX queries

Built NewPostForm - including CSS styling

Use a textarea so that post text will wrap

Currently not dynamically increasing size of box based on how much text th user has typed

Added currentUserProfileImg to top Header as well as NewPostForm

Notes

git add . vs git add -A

git add . checks nested folders, but does not remove deleted ones

git add -A checks nested folders and removes deleted ones

Try to keep State & store listeners higher up in the hierarchy, so can just pass as props down to children

Children just need to render props, don't need to listen to store

heroku log -t

Opens "tail" of Heroku log

heroku run rake db:migrate

Must migrate to production, otherwise tables won't have data, app won't render at all (error message says that "there is an error in the source code"