melvinlau / acebook-facebuzz Goto Github PK

Currently the like and unlike feature works but with page refresh. Next task, as required by client, is implement this without page refresh.

• Add username to User model
• Add username to signup
• Add username to User profile and posts
• Create alternative routes based on the username

Examples
https://codeclimate.com/
https://github.com/bbatsov/rubocop
https://github.com/colszowka/simplecov

Acceptance Criteria

When a user hasn't signed up and visits the index of the application:

• if they visit another URL, they are redirected to the index
• they can see a sign up page which prompts them to enter in their email address and password.
• they can only enter valid emails, otherwise they see helpful information to indicate why the email was not valid
• they can only enter passwords between 6-10 characters, otherwise they see helpful information to indicate why the password was not valid
• When they submit their details, they are logged in and redirected to their posts page with a message saying they were successful signing up

Resources

Rails: Look into https://github.com/plataformatec/devise as a way of doing this

Time estimate: 1/2 day
Sprint 2, Day 1/2

Test-drive CRUD features for Comments.
Time estimate: 1 day (Thursday 7 Nov, 9:30am)

Fields

• id
• post id
• message
• user id
• time created
• time updated

Choose one of the following:

• travis
  circleci
  jenkins
  codeship

Merge to master should run tests and deploy to prod

• Assuming tests pass, master should deploy to heroku/aws

Time estimate: 1 day
Day 1 of sprint 2

DESCRIPTION

• Posts and comments can be ‘liked’ and the number of likes is visible next to the post or comment

ACCEPTANCE CRITERIA

• A signed in user can:
• click on a ‘like’ emoji next to posts and comments to indicate a like, and can then click on it to remove that like.
• a count of likes shows next to the like emoji
• Users can like each post only once

Time estimate 1/2 day
Day 1/2 sprint 2

• Add wall id to posts table

• fix tests related to posting that will fail

Users should be able to edit the content of an existing post or remove it altogether.

FURTHER CHALLENGE

• the browser should not refresh when liking posts

All relationships will be defined. No migrations currently.

User can sign up/in. Posts need to be linked to logged in user.

Follow on from video : https://youtu.be/zJYuLebl-Js?t=449

7:29

Create tables for Users and Posts, relationships defined.

Pre-requisites

Users can sign up

Acceptance Criteria

• A non-signed-in user will be redirected to the index page.
• A signed-in user can:
• update their own posts for a maximum of 10 mins after they're created.
• see a helpful error message if they try to update another user's post
• delete their own posts.
• see a helpful error message if they try to delete another user's post

Requirements

• Run a database migration to associate a user to many posts
• investigate if any current data in any of the prod/dev databases would cause problems if tables were updated.
• Add new routes and controller actions
• https://guides.rubyonrails.org/routing.html#nested-resources

Time estimate: 1 day
Day 2 of sprint 2

• Heroku - nice readable docs, lots of magic under the hood
• AWS - good docs, but slightly more challenging to set up

Missed time estimate not completed in sprint 1.
Issue left unassigned

#1

As per above user requirement, passwords must be between 6 and 10 characters.

Pre-requisites

• User Can Sign in

Nice to have

• sign in via github

Time estimate: 1/2 day
Day 1 of sprint 2

Dependency of posts having a user id assigned to them

Time estimate: 1 day
Day 1 of sprint 2

DESCRIPTION

Users love your app so much they want to feel like they have their own space to manage on your social media platform!

ACCEPTANCE CRITERIA

• User is redirected to their wall when they log in
  /:user_id
• User can go to any /:user_id to see each user’s wall
• User can’t see any other user’s wall without logging in, User is redirected to login page
• User can see other users’ wall when logged in
• User can post on any user’s wall and the post only appears on that user’s wall
• User can not update or delete posts or comments apart from their own (on any wall)

FURTHER CHALLENGE:

• If the User doesn’t exist, handle requests to /:user_id by redirecting to a custom 404 page saying that the user doesn’t exist
• The User’s username can also be used to form the URL
  /:username

Pre-requisites

• User Can Sign Up

Acceptance Criteria

When a user hasn't signed in and visits the index of the application:

• if they visit another URL, they are redirected to the index
• they can see a link to a sign in page which prompts them to enter in their email address and password.
• they can only enter valid emails
• When they submit their details, they are logged in and redirected to their posts page.

BONUS CHALLENGE:
A User can choose between two or more different fonts AND background colours for their wall